March 9, 2006 at 11:46 am
Basically I want to have a "backup" copy of a database ready to go on a different SQL server in case the first SQL server is down, and I wanted an automated procedure to keep the backup refreshed. I was hoping to use replication, rather than trying to use a backup and restore, but when I tried to set up the publication it warned me that identity columns would not stay as identity columns, which seemed to me to mean that my application would no longer work on the "backup" processor.
What's the best approach to this, and why?
Thanks,
Dick
March 9, 2006 at 12:11 pm
Might be worth looking at log shipping.
March 12, 2006 at 5:49 pm
It depends on how up-to-date you want the database on the backup server, and how much data loss you can afford.
If you want it as current as possible, you're looking at replication or setting up a clustered server. If you use replication, you should be able to mark the ID columns as "not for replication".
If you can manage with it being a bit behind the main server then use log shipping and backup your logs every 5 or 15 minutes etc.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply