April 1, 2010 at 5:34 pm
Hi Folks
what would be the proper procedure, if any, to copy an SQL Server 2005 database from a Windows 2003 server to a brand new Windows 2008 Server running SQL Server 2008 ?
has anyone tried that ?
Thanks
Jim
April 1, 2010 at 5:45 pm
Do a backup on the 2005 server, copy the backup to the 2008 server, restore the backup.
If the DB if fully 2008 compliant, change the compatibility from 90 to 10.
There are no problems restoring a 2005 db to 2008 (except for possibly T-SQL SP's, or app code that uses pieces of code that have been dropped). But generally speaking, you should not experience a problem.
it almost goes without saying, test in the Dev and QA environments first.
/* ----------------------------- */
Tochter aus Elysium, Wir betreten feuertrunken, Himmlische, dein Heiligtum!
April 1, 2010 at 5:56 pm
Thanks GregoryF
can you expand on the Compliant change ?
Thanks
jim
April 1, 2010 at 6:01 pm
This means that a database is working correctly on SQL 2008.
You should do this in a dev environment first, then a UAT environment and test all of your applications.
Once you have UAT approval and User approval, then you can do the production upgrade.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
April 1, 2010 at 6:03 pm
There are certain T-SQL commands that are no longer supported with SQL2008, what comes to mind is the command DUMP (left over from the Sybase days), there may be some undocumented DBCC's that no longer work. However, to the best of my knowledge, if something was developed in 2005, it would not likely use 10 year old commands.
MSFT has an upgrade wizard that check a SP, Triggers, etc... to SQL 2008 compliance. Try it. Then all you would need to worry about is app code, for app code, you can run a trace, and replay it in 2008. But remember 2008, is not a major version change like 7.0 or 2005, it's more a minor change.
/* ----------------------------- */
Tochter aus Elysium, Wir betreten feuertrunken, Himmlische, dein Heiligtum!
April 1, 2010 at 6:22 pm
Run the upgrade advisor from 2008 to check for any code issues.
The above posts have covered the issues fairly well.
April 1, 2010 at 6:27 pm
Hi Steve
all my databases are on a Windows 2003 servere running SQl Server 2005 though
Jim
April 1, 2010 at 6:28 pm
Thanks
April 1, 2010 at 6:30 pm
what is SQL RNNR ?
Jim
April 1, 2010 at 6:35 pm
JC-3113 (4/1/2010)
Hi Steveall my databases are on a Windows 2003 servere running SQl Server 2005 though
Jim
Which means you would have to update to SQL 2008. Steve recommended that you run the upgrade advisor from SQL 2008 so you will know if you can upgrade those databases or not.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
April 1, 2010 at 6:35 pm
JC-3113 (4/1/2010)
what is SQL RNNR ?Jim
My blog and twitter handle.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
June 1, 2010 at 4:31 pm
Hi Folks
I need to re-visit this issue so hope you can help me
I was able to export a maint plan from, my sql server 2005 (windows 2003) using "File System" option. I then copied it over to my sql server 2008 (windows 2008) server manually, because i could not get SSMS Integration Services to do it.
Any way I got the plan imported, but what i do not understand is.. it still lists the databases from my sql server 2005, and does not list my new databaes on sql server 2008.
does anyone what i need to do to not see the old databases and see the new databaees ?
Thanks
Jim
Viewing 12 posts - 1 through 11 (of 11 total)
You must be logged in to reply to this topic. Login to reply