MVDBA (Mike Vessey) wrote:
Jeff Moden wrote:
Afaik and imo there are no pros only cons. There is no such thing as a "gap" in a primary key because 'unit consistency' is not a necessary attribute. Maybe others have a different opinion
I have worked with some folks that would disagree with us on that. They (some auditors that need to be take out for a pork chop dinner) think that any missing values in an ever-increasing column, such as an IDENTITY or SEQUENCE column means that someone deleted rows in an unauthorized fashion.
I'm not sure what a pork chop dinner is... I googled it and got a lot of recipies
I suppose your comment does bring up the issue of "soft deletes" - putting a "deleted flag" on a row - still doesn't stop failed inserts from creating ID gaps
Some of the folks saw a post I was involved in well over a decade ago and still identify with it. To make a really long story much shorter, some manager was whining about how to control a Developer. It appeared that he had little in the form of calcium in has back (no spine). Everything that people offered him as a suggestion only increased his whining because the Developer was (in his words, not mine) "valuable".
I wrapped up my conversation by explaining that sometimes you have to take such people out for a "pork chop dinner"... which occurs in the woodshed... and the developer is tied to a chair... and you feed the developer frozen pork chops using a 3 banded Wrist-Rocket slingshot at point blank range to keep his attention between explanations.
That gave birth to terms like "pork chop launcher" and "high velocity pork" and, of course, "pork chop dinner". It's definitely an "inside" understanding by some of the very long term denizens of SQLServerCentral.