May 19, 2008 at 9:18 am
Hiya,
Thought I would run this through people on here to get their opinions. I have a DTS job that will be scheduled to run once a week. It populates a table on Server A, and this data pumps to Server B and C.
Now when B and C have been populated, I want jobs running locally on there to use this new data to manipulate a set of existing tables.
Now the tricky-ish part (or maybe not)...
Once these jobs have been run on Servers B and C, I need server C to run the "finale" of the job. That being, resetting some status tables and putting replication subscriptions back in place.
My issue is how to get this to trigger. My idea at the moment is to have another job on Server A that runs every 10 minutes. It searches for the criteria to be met on Server B and C, and if both have been met, it goes off does its stuff. If for some reason the jobs on B and C fail, it needs to put replication back in place as a minimum.
How can I go about this? Any simple pointers to put me on the right path? I'm not sure on scheduling existing jobs on the fly in T-sql, and I'm not sure about checking if a job has failed either.
May 19, 2008 at 3:34 pm
Did you try to set DTC (Distributed Transaction Coordinator) in MS SQL between servers?
May 19, 2008 at 4:01 pm
Maybe you could expand on that a little to apply DTC to my case?
Thanks for your help
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply