I think it's actually worse than you say. If you look at some of the horrendous problems on CONNECT that occurred with 2012 and the continuing lack of attention to detail in preserving functionality even in SSMS, it would seem that MS has come to using SPs and CUs as a crutch for poor programming practices, inadequate testing, and a lack of good source control.
Don't get me wrong. I think that SQL Server is one of the best RDBMSs in the world but, if MS would start doing things right, it could be the best. Not sure that's possible in the next 10 years, though, because of all the technical debt they've built up by postponing fixes and releasing partial functionality like that damned PIVOT function and, up to 2012, the horrible job they did on the Windowed Functions and (especially) the related aggregates.
And then there's the "cloud". Good grief.
is pronounced "ree-bar
" and is a "Modenism
" for R
ow.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.
Dear Lord... I'm a production DBA. Please grant me patience because, if you grant me strength, I'm gonna need bail money to go with it.
Helpful Links:How to post code problemsHow to Post Performance ProblemsCreate a Tally Function (fnTally)