Bharatvip (5/11/2016)

---

We are moving 6 production databases from one physical server to another. The drive numbers and names on the new and old servers do not match up, but we will be able to take care of that.

My question is:

On the weekend of the move, what is the best way to stop servers in order to be sure that all transactions that were started are committed before we take the backup of the databases on the existing prod. Move the .bak files to the new server and restore them there.

Should the web servers get stopped first and then the database server? Also, on the database side, is it sufficient to run DBCC OPENTRAN to make sure there are no open transactions and then maybe put the sql server on single user mode and make backups of the 6 databases.

If we go the route that has been mentioned above, is it ok to just take full backups of the 6 databases and restore with replace option on the new server and not worry about copying/doing anything with the transaction logs on the source(old server)? As we would have kind of made sure all open transactions closed before making the backup, so don't need anything from transaction logs applied.

Appreciate any advice from folks who have been there...done that.

Thanks,

bvip.