Hi All,

I have an SQL server 7 under Windows NT4 with about 30 dBs (around 90Gb) +
jobs to migrate to SQL7/Windows2000.

I wonder if somebody faced any problem during a migration and decided to go
back to the former server after one day production or more on the new
server.

How can I be back onto the former server, minimizing the impact on the
production side and of course with latest possible data available?

Do you have any idea of script that might help me?

Recovering with the latest backup, but what about transaction files on the
new server or index which could be the cause of the mismatch?

For my migration plan I did not covered this option...and now I'm scared.



Thanks for your help.



Regards,Serge.


MS Sql Server LazyDBA home page