July 25, 2007 at 7:30 am
We have a 5-year-old server that is out of warranty and may require a long wait for someone to come and repair it. It is running SQL Server 2000 Standard. Thankfully, it does have RAID-5.
We have a newer server running SQL Server 2005 x64 Standard that has a database running with the same name as the database in the older server for testing; eventually it will be used exclusively. It, too, has RAID-5
For right now, however, we need to have as little downtime as possible if the older server goes down. What is the best solution so that we have a minimum of data loss as possible if the older server goes down? I've looked at replication, log shipping, and some third-party solutions, but I thought I'd get some impartial advice.
July 25, 2007 at 8:23 am
Detach/attache method will work fine. Also the backup and restore methids. Then you can move the logins and jobs and other things by scripting out and executing in the other server.
Cheers,
Sugeshkumar Rajendran
SQL Server MVP
http://sugeshkr.blogspot.com
July 25, 2007 at 8:54 am
Well there some information you didn't provide which would be handy in answering a question like this. Specifically, does the database on SQL Server 2005 need to be usable? If not then I'd simply implement log shipping. If the database is rarely updated then you could perform log backups every 15 minutes or so. If the database is updated very frequently and/or the SQL Server 2005 database must be accessible then transactional replication might be the best answer.
I find that transactional replication tends to be slightly more difficult to setup and manage than log shipping so that might factor into your equation as well.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply