ALZDBA (2/1/2009)
Jeff Moden (1/31/2009)
That little privs change on sp_MakeWebTask killed a lot of people's code because it now requires "SA" privs and a lot of smart DBA's won't allow users or procs to have "SA" privs. And I can't wait to see all the code that breaks when they finally fix SUM() OVER and all the poor buggers currently using it in their code have to go back and fix things.If there are bugs in the system, I'm glad they (ms) fix it.
Maybe the fix isn't what we would like it to be, but if it closes weak parts of the implementations, they should post a remark for this behaviour, so we can prepare for the impact.
And because we all have a nice system of Test -> QA -> EnduserTest -> Prod 😀 , this kind of problems should arrise before it shuts down any production revenues.
What is important, is that you know you are using an undocumented whatever and that you have to check its availability / operational status with every sp, hotfix, new realease, ... and be prepared to pay the price if they throw it away.
So first try to figure out the proper way before going to any darker side. 😉
And THAT is what I'm really getting at... it doesn't matter if it's an undocumented feature or not! If you don't do any regression testing before you drop a "fix", sp, or whatever into your production system, you're begging for "Death by SQL" even if you haven't used any undocumented features.
It's not the use of undocumented features that will kill you... it's any change even on fully documented features. You must test before making any patch or sp to SQL Server or at least be very, very aware of what the impact will be.
--Jeff Moden
Change is inevitable... Change for the better is not.