April 2, 2010 at 11:17 am
I have sql 2005 and we have couple of jobs for one database used by
support team.we have mirroring set up on that db.
Server-A (principle)
Database -A --> has 10 jobs right now.
-------------------
Server -B (mirror)
Database -B --> also has 10 jobs right now.
But support team is adding/modifying these jobs on server-A.
We have to make sure that jobs on both servers are identical all
the time.
So whenever addition/change happens, we have to make sure both servers
are in synch. How can I achieve this?
I cant create Triggers on system tables like sysjobs.
Also I cant use SSIS 'Transfer jobs task' which can overwrite my all
jobs.(I just want to move those jobs who are newly created or modified)
any suggestions are appreciated. Thanks
April 2, 2010 at 11:26 am
Could you use TableDiff (comes with SQL Server 2005)? Pull information about the configured jobs of each server to a temp table (or compare the sys tables straight, but don't know if I would do that) and then use TableDiff to compare the configured jobs found. If one is different or "new" then notify by email or some type of alert.
Shawn Melton
Twitter: @wsmelton
Blog: wsmelton.github.com
Github: wsmelton
April 5, 2010 at 7:50 am
dallas13 (4/2/2010)
But support team is adding/modifying these jobs on server-A.We have to make sure that jobs on both servers are identical all
the time.
What kind of chages support team do ?
if changes are related to TSQL then u can put them in stored proc and whenever somebody make chages then changes will be replicated to other side (keep those Sp in mirrored DB)
BUT if Support team do changes in JOB's setting then i think that will need to do manually.
-------Bhuvnesh----------
I work only to learn Sql Server...though my company pays me for getting their stuff done;-)
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply