Heh... I'm no longer surprised by such things. For example, the came out with EOMonth, which has the very problem we're talking about. They didn't come out with an SOMonth or BOMonth function, though. ISOWK has been out for more than a decade and they still don't have a function to convert to a date range. And the things they did to the newer date type (DATE, TIME, DATETIME2) are just horrendous. Then you look at things like the train-wrecks they call PIVOT, FORMAT, STRING_SPLIT, SSMS loss of functionality (and it continues), and, going way back, the removal of things like sp_WebTask, SP's and CU's that blow things up (Online Clustered Index Rebuild cause corruption in 2012 prior to sp2 IIRC, for example), improvements like the Cardinality Estimator (killed me), making it so I can't disable the equivalent of TF 1118 on TempDB, and the performance train-wreck of 2017 RTM (and many others), etc, etc, you'll understand why I've become a little numb to it all.
My only saving grace in some of this is to constantly repeat "A'm workin' for ah livin' so A'm takin' what dey givin'". 😀 I'd retire but I'm having too much fun watching stuff like this happen for real.
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)