SQL Server Performance Forum – Threads Archive

Going Back from 2005 to 2000

Hello,
We are going to change our SQL 2000 for a new (physical) server with SQL 2005. We need a plan so, if something goes wrong, we can go back to SQL 2000. The process will be to stop SQL 2000, backup DB and then restore it on SQL 2005 and beging operating with the new server. The problem is that, if we find any problem we will go back to SQL 2000, but we need to pass the new information that is in SQL 2005 but not in SQL 2000. We can not do a backup in SQL 2005 and restore it on SQL 2000. Can anybody offer us any solution?. We are thinking on having any utility like Log Explorer or something like that to get all the transactions form the Log in SQL 2005 and then re-execute then on the SQL 2000.
Thanks a lot for your help.
Luis.

http://weblogs.sqlteam.com/mladenp/archive/2007/02/15/60101.aspx _______________________________________________
Causing trouble since 1980
blog:http://weblogs.sqlteam.com/mladenp

Hello spirit1,
Thanks a lot for your help, I am going to try to do what is says to see if that solution is ok for my system.
Luis.

how about transfering data from SSIS. you can do a lookup and transfer data which is not in 2000 but in 2005
—————————————-
Contributing Editor, Writer & Forums Moderator
http://www.SQL-Server-Performance.Com Visit my Blog at
http://dineshasanka.spaces.live.com/

Don’t forget to visithttp://www.sql-server-performance.com/forum/topic.asp?TOPIC_ID=19622 very useful. Satya SKJ
Microsoft SQL Server MVP
Writer, Contributing Editor & Moderator
http://www.SQL-Server-Performance.Com
@http://www.askasqlguru.com/ This posting is provided AS IS with no rights for the sake of knowledge sharing. Knowledge is of two kinds. We know a subject ourselves or we know where we can find information on it.

You can also set up replication from 2005 to 2000 servers as a backup option. ***********************
Dinakar Nethi
***********************
http://weblogs.sqlteam.com/dinakar/

Hot from oven,<a target="_blank" href=http://sqlserver-qa.net/blogs/tools/archive/2007/07/20/downgrade-or-revert-or-restore-sql-server-2005-database-to-sql-server-2000-version.aspx>http://sqlserver-qa.net/blogs/tools/archive/2007/07/20/downgrade-or-revert-or-restore-sql-server-2005-database-to-sql-server-2000-version.aspx</a> blogged the process to revert back. [<img src=’/community/emoticons/emotion-1.gif’ alt=’

‘ />] Satya SKJ Microsoft SQL Server MVP Writer, Contributing Editor & Moderator http://www.SQL-Server-Performance.Com</a> @<a target="_blank" href=http://www.askasqlguru.com/>http://www.askasqlguru.com/</a> <center>This posting is provided AS IS with no rights for the sake of knowledge sharing. <hr noshade size="1">Knowledge is of two kinds. We know a subject ourselves or we know where we can find information on it.</center>

you and your oven…hehe<img src=’/community/emoticons/emotion-1.gif’ alt=’

‘ /> Michael MCDBA "The statistics on sanity are that one out of every four persons is suffering from some sort of mental illness. Think of your three best friends — if they’re okay, then it’s you!"

[<img src=’/community/emoticons/emotion-5.gif’ alt=’

‘ />]why not… what do you think? <blockquote id="quote">quote:<hr height="1" noshade id="quote">Originally posted by MikeEBS you and your oven…hehe<img src=’/community/emoticons/emotion-1.gif’ alt=’

It is well done. Just the choice of words for the brain<img src=’/community/emoticons/emotion-1.gif’ alt=’

‘ /> LOL Michael MCDBA "The statistics on sanity are that one out of every four persons is suffering from some sort of mental illness. Think of your three best friends — if they’re okay, then it’s you!"

Hi Everybody,
Somebody has told me a new possibly solution. 1.- Set Log Shipping between 2000 (publisher) and 2005 (subscriber)
2.- On ‘D’ day cut off Log Shipping
3.- Set tansactional replication between 2005 (publisher) and 2000 (subscriber) I will let you know if the test works fina. Thanks to everybody for your help… Luis.

Yes, it is possible solution…
But step 3 which setting transactional replication from 2005 to 2000 should be fine but all objects should have the primary key and for smaller dbs it should be fine…
MohammedU.
Microsoft SQL Server MVP
Moderator
SQL-Server-Performance.com All postings are provided â€œAS ISâ€ with no warranties for accuracy.

That is what Dinaker referred above [<img src=’/community/emoticons/emotion-5.gif’ alt=’

‘ />] <blockquote id="quote">quote:<hr height="1" noshade id="quote">Originally posted by luisinfo Hi Everybody, Somebody has told me a new possibly solution. 1.- Set Log Shipping between 2000 (publisher) and 2005 (subscriber) 2.- On ‘D’ day cut off Log Shipping 3.- Set tansactional replication between 2005 (publisher) and 2000 (subscriber) I will let you know if the test works fina. Thanks to everybody for your help… Luis. <hr height="1" noshade id="quote"></blockquote id="quote"> Satya SKJ Microsoft SQL Server MVP Writer, Contributing Editor & Moderator http://www.SQL-Server-Performance.Com</a> @<a target="_blank" href=http://www.askasqlguru.com/>http://www.askasqlguru.com/</a> <center>This posting is provided AS IS with no rights for the sake of knowledge sharing. <hr noshade size="1">Knowledge is of two kinds. We know a subject ourselves or we know where we can find information on it.</center>

]]>