Steve Jones - SSC Editor wrote:
Voting forces a choice. Do I want A, B, or C. consensus allows me to say A, but not B, C is OK. We can come to a choice around C, or the others, with a group.
Ranked choice voting, multiple votes, etc. are other ways you can build a consensus. It involves discussion and debate over just making a decision.
The BIG problem is who the people are that are doing the voting. For example, what the hell were people thinking when the made the equivalent of TF 1117 totally non-optional for TempDB??? I can certainly understand making it a default for people that don't know any better but there are times where it makes things impossible. For example, if you need to use SET IDENTITY INSERT ON for a large table, there's a fault that, even with minimal logging, the whole bloody table gets sorted in TempDB. If you have an 250GB table like I had to do, that means that all 8 files that I have expand to 250GB! It would have been nice to temporarily set TempDB to NOT expand all files equally for that one evolution but, no, a bunch of people somehow convinced MS that would never be necessary.
And then there's the people that designed String_Split()... again... what in the hell were they thinking? And then the painfully slow FORMAT function and the idiocy known as PIVOT, SHRINK FILE (with index inversion), Index Rebuild, Index Reorganize, defaulting LOBS to "in-row", integer dates and times and having them in separate columns (to add insult to injury) in MSDB, Temporal Tables with no embedded Modified_By, and removing the ability to do direct date math on any of the newer temporal data types, making in-memory non-reversible for file group usage, and forcing a wicked poor and flat out wrong wording in BOL that are responsible for supposed index maintenance "Best Practices" that millions of people have made the mistake of adopting, "fast inserts", etc, etc, etc. The list is too big to post here.
And then there are things like having a built in sequence generator have been open but no action taken for more than 11 years now.
The point is that whether it's by vote, by consensus, or "professional" opinion, some huge mistakes have been made and there's no damned plans to fix them and the good ideas that come from the field of pros at large are never even considered because the people making the decisions aren't actually qualified to do so or have an agenda based on some hair brained marketing strategy. "Ribbon Bar" in office? What a freakin' joke. Let's quadruple the number of clicks required to get to the same old menus... way to go! And, for the errors they induced in SSMS when it became a separate product, someone should be driven out of the business never to go near a computer ever again.
is pronounced "ree-bar
" and is a "Modenism
" for R
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.
"Change is inevitable... change for the better is not".
"Dear Lord... I'm a DBA so please give me patience because, if you give me strength, I'm going to need bail money too!"
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)