Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. 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

We're currently using Clustering to do fail over for our SQL environment.

There are two servers that use the same shared drive. The SQL database is on a shared drive. This provides OS and hardware failover, however there is only a single copy of the database.

What we need is two copies of our database. We need this to allow us to roll changes into production safely. The deploy process would be to have one the web server point at one SQL Server, while we failover the other server to do the deployment. Then we would point reverse this configuration to update the first SQL Server.

Does anyone know how to use clustering to do that?

share|improve this question

migrated from Mar 6 '12 at 23:38

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

I think you're missing the point of clustering. There is one and only one shared database on your common drive. There is no "offline" copy of the database on the passive server. – Joe Stefanelli Mar 5 '12 at 22:23
Mirroring ( and replication ( are alternatives, neither of which quite does what I think you're looking to do, but both involve two copies of a database. There's a good discussion of both here: – Paul Karlin Mar 6 '12 at 6:28
It sounds as though your general process is a bit flawed for deployment to production. – Thomas Stringer Mar 7 '12 at 1:46
Please add to the question the details of the deployment process you are currently using and the challenges faced with trying to deploy to a "live" system and not an "offline" one. – Jason Cumberland Mar 7 '12 at 14:56
up vote 1 down vote accepted

General rules for deployment would have kinks worked out when deploying to a TEST, QA or DEV system so there are no issues with the PROD deployment. If you are already running a cluster you can add an instance to the cluster at no licensing cost and use that as your TEST environment to iron out the deployment process. If the deployment to TEST goes south then you simply restore the database from the PROD backup, change the scripts and try again.

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.