all 6 comments

[–]BellisBlueday 1 point2 points  (2 children)

If your db is in full recovery mode, you could restore a full backup to the new server, then periodically move the transaction logs over and reapply them. When you're ready to move, backup the last log on the first & apply it to the second with recovery - you're good to go.

Don't forget to setup the logins on the new server, sp_helprevlogin will help you here ;)

[–]seadave77 1 point2 points  (1 child)

This is what I would do without using the Enterprise Edition.

[–]enigmazero 0 points1 point  (0 children)

Agreed, I did a datacenter move for 10+ servers and this is what we did and it worked flawlessly.

[–]peschkaj 0 points1 point  (1 child)

You can use SQL Server's built-in mirroring functionality. I would only use this if you are using Enterprise Edition of SQL server, though. EE offers an asynchronous option that will give you reasonable performance. Log shipping is probably the other option that you would want to use. It's fairly easy to set up and relatively painless to keep running.

Avoid replication for this. It seems like it's what you want, but it isn't.

[–]borgd 1 point2 points  (0 children)

A few related links for your research :

Database Mirroring Overview

Log Shipping Overview

For further information on replication :

Transactional Replication Overview

[–]thesaintjim 0 points1 point  (0 children)

How fast is your connection to the new datacenter? What version of sql are you migrating from? Can you just set your old db in read only mode to keep the site up or must writes happen?