Upgrade SQL2ksp4 to SS2005 keeps master dblevel 80 ??
-
After upgrading a SQL2k sp4 to SS2005 sqlsmo shows master
Dim oDatabase As new mySQLSMO.Database
'Get the database
oDatabase = globSMOSrv.Databases.Item(
"master")
in VS2005 immediate window
?oDatabase.CompatibilityLevel Version80 {80}
Why is this ???
What will be the effect if I change it to 90 ?
Johan
Learn to play, play to learn !Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:- How to post Performance Problems
- How to post data/code to get the best help[/url]- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution 😀
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me
-
When you upgrade or restore a 2000 database to 2005, the dblevel is unchanged (80). You need to manually change to 90 if you want to use 2005 features.
-
The strange thing is that I can implement storedprocs that use e.g. CTE's and execute them without a problem or warning
Johan
Learn to play, play to learn !Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:- How to post Performance Problems
- How to post data/code to get the best help[/url]- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution 😀
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me
-
compatibility level is set for individual database, not for the server. Are you sure you are working on and checking the same database? From your smo code, you are checking master database.
-
globSMOSrv = the smo.server
as stated in the first of this thread :
oDatabase = globSMOSrv.Databases.Item("master")
in VS2005 immediate window
?oDatabase.CompatibilityLevel
Version80 {80}
?globSMOSrv.Information.VersionString
"9.00.1399.06"
Now what's the point of not having at least the system databases fully upgraded to SS2005 ?
Johan
Learn to play, play to learn !Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:- How to post Performance Problems
- How to post data/code to get the best help[/url]- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution 😀
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me
-
Got your point. Sounds like a bug. Right now I don't have an upgraded server so I cannot confirm it.
-
I've just installed 2005 over a dev copy of 2000. It faild to install Reporting Services base on the Master db compatibility level being 80.
My questions are how do I check and then alter this level in 2005? and once i've changed it can I just install Reporting Services on it's own?
Howard.
-
I guess you can alter the system-db's dblevel without a problem.
You'll also notice the (db) reports for e.g. space usage, will not work, but give you an errornotification that the dblevel has to be set to 90 !
Once that has been done, these reports work fine.
Johan
Learn to play, play to learn !Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:- How to post Performance Problems
- How to post data/code to get the best help[/url]- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution 😀
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me
-
sorted,
I ran EXEC sp_dbcmptlevel 'master', 90 and then just tried to reinstall reporting services. Worked a treat.
Cheers.
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply