May 11, 2003 at 9:00 pm
Hi there
At the end of the day, think "simplicity". Log shipping is very simple, and yes, you can get small glitches from time to time (typically related to disk space issues or errors on copy), but the key is that its very easy to administer. We do change controls each wed night, lots of db changes, so my custom log shipping dts simply redoes the full and starts again. Unless there is a really well defined need for it, replication is not my choice.
Cheers
Ck
Chris Kempster
www.chriskempster.com
Author of "SQL Server Backup, Recovery & Troubleshooting"
Author of "SQL Server 2k for the Oracle DBA"
May 13, 2003 at 8:15 am
quote:
Hi thereAt the end of the day, think "simplicity". Log shipping is very simple, and yes, you can get small glitches from time to time (typically related to disk space issues or errors on copy), but the key is that its very easy to administer. We do change controls each wed night, lots of db changes, so my custom log shipping dts simply redoes the full and starts again. Unless there is a really well defined need for it, replication is not my choice.
Cheers
Ck
thanks for your input. I too think log shipping is a simple way to maintain a warm standby server
May 14, 2003 at 8:43 am
actually you should use what is best for the situation, we have a database with 30000 tables in it which can only be logged shipped, but because it can create logs bigger than the bandwidth to copy you have to keep manually copying the logs
On our other databases we use merge replication. But in an active passive setup. If the server fails, we make a dns change to the merge replicated database. Then when the other database is backup, merge replicates back to the primary database and we change the dns back.
May 20, 2003 at 3:45 pm
quote:
actually you should use what is best for the situation, we have a database with 30000 tables in it which can only be logged shipped, but because it can create logs bigger than the bandwidth to copy you have to keep manually copying the logsOn our other databases we use merge replication. But in an active passive setup. If the server fails, we make a dns change to the merge replicated database. Then when the other database is backup, merge replicates back to the primary database and we change the dns back.
Another issue with log shipping is cost, u need Enterprise Edition and that costs a lot if u are running 2 dual machine servers
-sk
Viewing 4 posts - 16 through 18 (of 18 total)
You must be logged in to reply to this topic. Login to reply