June 16, 2009 at 8:32 am
Hi there.
A client of mine recently requested that we setup 2 SQL 2008 Servers, one for a fail over.
I've setup SQL Servers before, but never before have I setup a redundant SQL server.
Does anyone know where I can get some documentation on this?
Thanks muchly.
June 16, 2009 at 8:47 am
Always start with Books Online. They always have the basics in there. After that, there are some good whitepapers on Log Shipping and mirroring on MSDN
June 16, 2009 at 8:49 am
R u planning to implement Mirroring (Like ur subject says)on ur other SQL Server?
If yes, Install SQL on ur other box, take up full backup of ur Active server A, then restore using norecovery in Server B. Do the same for Log backup.
The set up Mirroring by going on individual database, Properties in Mirroring Tab.
August 19, 2009 at 4:20 pm
You may want to look at transactional replication.
September 14, 2009 at 2:15 pm
As a fail-over are they talking high availability or just redundancy as these are two different scenarios. Clustered, Mirroring, Replication, log-shipping ... The question is far too broad to provide any sort of adequate answer.
October 30, 2009 at 8:31 pm
If you're looking for no data loss and automatic failover then mirroring is sometimes a good option. The thing to watch out for here is the version of SQL that you have, standard or enterprise. Standard only supports synchronous replication while enterprise supports asynchronous. If your servers are located in different sites (i.e. over a slow connection) the latency involved with synchronous replication can slow down your application since the principal database server has to wait on the mirror to commit and respond back. If both servers are of similar hardware and have a high speed connection then synchronous replication shouldn't slow things down any.
The automatic failover feature in mirroring involves a witness server and this role can be performed by a SQL Express database installed on a third server if necessary. Something else I think you have to watch out for with mirroring is if you don't have a witness server the mirror server going offline can take your principal server off-line too since you can't achieve quorum with only one of two. Also, automatic failover does you no good if the application is not 'mirror aware'.
If you don't need automatic failover then transactional replication works just as well to provide for a good copy of the database on a different server. Log Shipping is only as current as the last log file shipped to the secondary server, if you can't get at the transaction log file in order to get a tail log backup.
Hope this helps point you in the right direction. Once you choose a solution then as stated before, Books Online is the best place to get started.
Steve
SQL Managed
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply