Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

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 setting up a Standby Server for disaster recovery and high availability reasons. My product relies heavily on SQL Jobs, as such, these jobs need to exist (Disabled) on the Standby server.

I have the database replication setup, however I can't find information on techniques for syncing jobs between two servers.

Does anybody do this, and what techniques can you suggest?

I'm currently using SQL Server 2005.


share|improve this question
up vote 2 down vote accepted

In SSIS there's an SSIS task that can transfer all jobs, or just specific jobs. You can tell it to overwrite the jobs, or fail if they exist, and handle the job deletion your self. Schedule this as a job to run nightly, or make it a part of your job release process to run this job after a job has been changed.

You'll want to add a SQL task after the jobs have been transferred to disable them using the procedures in the msdb database.

share|improve this answer
Perfect, thank you, does a similar task exist for logins and users? – MrEdmundo Sep 14 '09 at 19:33
For Logins yes. Users are stored within the database and will come across with when the database is restored. – mrdenny Sep 14 '09 at 21:26

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.