Comments on: Supermarket Seeks and Scans

By: chern yen tan

chern yen tan — Sun, 18 Oct 2020 21:29:24 +0000

This is brilliant! Thank you!!!

By: Kanishka Basak

Kanishka Basak — Wed, 14 Oct 2020 11:04:50 +0000

This was a really good one. Thank you for explaining the DB world with a real life example!

By: Rob Farley

Rob Farley — Tue, 13 Oct 2020 20:18:50 +0000

In reply to Glenn Berry. I haven’t missed one yet, not in any of the 131 T-SQL Tuesdays.

By: Glenn Berry

Glenn Berry — Tue, 13 Oct 2020 20:17:36 +0000

Good post Rob. Thanks for contributing again this month!

By: Rob Farley

Rob Farley — Tue, 13 Oct 2020 20:03:30 +0000

In reply to M McDonald. I mention corruption because it’s useful to know that a a table can still be used even when there’s corruption if the spot where corruption is doesn’t get touched. A busy (or locked) aisle can cause waits that can slow down the activity even if it doesn’t cause an error, so I’d say the analogy definitely works with that too. There’s a lot of ways this analogy stretches, and if nothing else, it can make for some great discussions. I’m pleased you enjoyed it.

By: M McDonald

M McDonald — Tue, 13 Oct 2020 17:48:27 +0000

I very much enjoyed the analogy with one comment:

I mentioned a minute ago that I wasn’t going to go down the confectionary aisle. Good thing too, if there’s a problem there. I’m sure we can all imagine the times when there’s a problem down a particular aisle… analogous to a page corruption in a database, but if I didn’t have to go there, then I can still do what I need to without being affected.

A problem on the confectionery aisle may not be corruption (LOUDSPEAKER — “CLEAN UP AISLE 5”), but a hot spot or location of heavy activity (sale on sugar and cake mixes). Heavy activity in that area is not important important in relation to your shopping list but if is there is a mess (corruption) someone still has to clean it up…

Or did I over think it?