September 12, 2008 at 7:55 pm
Comments posted to this topic are about the item Is it 1995?
September 15, 2008 at 3:27 am
For clarity, the problem was originally reported here -
http://www.sqlservercentral.com/Forums/Topic560965-391-1.aspx
I'm more surprised this survived all the testing that was done on 2008. Seriously, in all the automated tests that were run nightly for months, was there no test case for upgrading under non-standard conditions (like the sa renamed)?
We can't even make the excuse that is was old code that crept into the upgrade, as the code that actually breaks (as opposed to the 4 places it's hardcoded that doesn't break) was on the creation of a job to clean out history of the policy-based management. Not exactly a 2005 feature.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply