Take a look in BOL at Log Shipping. The backup server can be kept up to date with the primary server. You control how often the data changes are applied to the backup. It's probably the most cost-effective way to have a 'warm' backup at the ready.
You can either use SQL Servers built in Log Shipping, or you can write your own. I recommend writting your own code to do it. I've found that it's much easier and more reliable then using the built in log shipping. The end result is the same.
Denny
--Anything is possible. All it takes is a little research. (Me)
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.