Monday, September 13, 2010

Options Creating Accounting Failover Backup Server

Replication
  • For each identity column in the publisher database, the identity column needs to be changed from "Yes" to "Yes (not for replication)" details...
  • This would be extremely tedious considering that it must be done manually in SQL Server 2000
Log Shipping
  • Recovery model must be changed from Simple to either Bulk-Logged or Full
  • Changing from Simple will cause the transaction log to fill up more quickly, become prohibitively full unless backed up efficiently, as the transaction log gets truncated when the database is backed up
UPDATE: Backups are running daily at noon, this solves the problem of transaction logs becoming too large. Log shipping appears to be the most viable option at this point.