compatibility level of master database

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

asked Mar 08 '10 at 11:44 AM in Default

Rob 2
57 ● 3 ● 3 ● 3

Looking forward to answers. I wouldn't have thought this was even possible.

Mar 08 '10 at 12:03 PM Grant Fritchey ♦♦

+1 on question and Grant's comment. Like... WTF??

Mar 08 '10 at 12:53 PM Matt Whitfield ♦♦

+1 Grants comment

Mar 08 '10 at 01:21 PM CirqueDeSQLeil

(comments are locked)

6 answers:

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.

answered Mar 08 '10 at 06:32 PM

Rob Farley
5.7k ● 13 ● 17 ● 19

(comments are locked)

The MSDB contains: - DTA tables, it turn-out that an old version of DTA didn't deleted its tables, for a cleanup script read http://support.microsoft.com/kb/899634 - repository tables of version 7! (like RTblClassDefs)

so these are SQL server related tables.

answered Mar 09 '10 at 07:37 AM

Rob 2
57 ● 3 ● 3 ● 3

(comments are locked)

I found out that the master AND the msdb are being used as user databases!

answered Mar 09 '10 at 04:02 AM

Rob 2
57 ● 3 ● 3 ● 3

(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).

answered Mar 08 '10 at 02:54 PM