Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I am trying to set up a transactional replication database on two MSSQL 2008 Standard servers. We need to be able to query off of the subscriber database, but we would also like to be able to use the subscriber as a backup if the primary server fails.

Is it at all possible to use the subscriber database, if it is replicating ALL of the data from the publisher, as a backup primary database, or do I need to use some other form of replication/mirroring that still allows near real-time querying?

share|improve this question

migrated from Jun 17 '11 at 9:13

This question came from our site for professional and enthusiast programmers.

Probably better question for – lazyDBA Jun 16 '11 at 20:34

You need to ask yourself some specific questions on what you want then it will be easy to use the right solution.

Do you want to read the data from the secondary in real time? Do you want to be always connected to the secondary or is it ok to get disconnected for few seconds to sync from primary? Do you want to do this for one db or for 50 databases? Do you want to switch to the secondary when primary fails automatically? Or do you want this to handle manually and sometime delay is fine here?

Based on the above, you can determine if you need log shipping/ database mirroring/replication.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.