July 5, 2006 at 1:29 pm
I never noticed it before, but I am now using Management Studio to administer our sql databases. One of them located on a sql 2000 server, says "6.5 compatible", when viewed from Management Studio (but not from Enterprise Manager).
What are the step needed to upgrade the database? (I think I need to run the Sql 2005 Upgrade Advisor first, fix any errors found, then manually change compatibility mode (to 80) from the sql 2000 server where the database is located.)
TIA,
Bill
July 10, 2006 at 8:41 am
I don't have a 6.5 server to test this but it could be the 6.5 on your 2k has a 6.5 collation - this might be the problem.
In 2000 under database properties ( in EM ) you can set compatibility - I suggest you check the setting here and the collation.
Other than that detach and attach to a test 2005 server and change the comaptibility to 2005 and see what happens.
Yes the wizard may help. Always be wary of using 2005 tools against earlier versions of sql server.
[font="Comic Sans MS"]The GrumpyOldDBA[/font]
www.grumpyolddba.co.uk
http://sqlblogcasts.com/blogs/grumpyolddba/
July 10, 2006 at 8:44 pm
"Always be wary of using 2005 tools against earlier versions of sql server."
Can you please amplify that remark?. I always thought that backward compatibility (except for deprecated keywords, sql constructs and stuff like that) was a given!
TIA,
Bill
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply