|
Ik have a SQL server 2005 database with a master database with a compatibility level of SQLServer 2000 (80). Why would someone do this? Can I change this without a risk? Any suggestions would be helpfulle, because I can't imagine why this has been done. Rob
(comments are locked)
|
|
Someone may have implemented a proc in master that doesn't work in 2005. I know a few third-party applications thar put code in master. So... you can change it, but you definitely run a risk of breaking something.
(comments are locked)
|
|
I think the best answer for you right now would be to try and replicate the environment. Setup a server and set a master database to compat 80. Change it back to 90 and then test for any issues. I'm with Grant and Matt on how this could even have happened - or why. Just tested it personally (also had some other Ninja's test and they concur) - set it back immediately.
(comments are locked)
|
|
I'll post it, but I won't take credit for it. According to Gail Shaw, this is no big deal. Someone was messing around or screwed up, but you can just fix it. "Someone being stupid. I'd say set it back to 90 immediately." For what it's worth. I'm fairly certain she's right (she usually is). +1 @ Grant Shaw :)
Mar 08 '10 at 06:00 PM
Matt Whitfield ♦♦
(comments are locked)
|
|
I found out that the master AND the msdb are being used as user databases!
(comments are locked)
|
1 2 next page »
Looking forward to answers. I wouldn't have thought this was even possible.
+1 on question and Grant's comment. Like... WTF??
+1 Grants comment