July 31, 2007 at 3:34 pm
What kind of back out plan should be employed to apply transactions/data differences made in SQL2K5 back to SQL2K should we decide to back out and flip our switches back to SQL2K? Detach and attach? Restore?
July 31, 2007 at 4:19 pm
Create blank databases and use DTS to copy your data back, all other solutions will not return your original databases because the product changed in many ways. Hope this helps.
Kind regards,
Gift Peddie
July 31, 2007 at 11:48 pm
Miss -
You cannot take an entire database "back" from SQL 2005 to SQL2K - detach attach, backup/restore just won't work.
The DTS suggestion is reasonable as long as your SQL 2005 database doesn't use any of the new datatypes, schemas, index options, etc.
One thing that may help is to keep the compatibility level of the SQL 2005 database set to SQL 2K level (8.0).
Joe
August 1, 2007 at 5:51 am
If your 2005 server is a new server or a new instance and you can leave the old one running, you can actually replicate (assuming all of your tables can be replicated) from the 2005 server to the 2000 server until you are comfortable that the new server is working correctly.
August 1, 2007 at 2:38 pm
What would some of the risks be behind replication? Would it be easier to use triggers to update our tables?
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply