June 4, 2008 at 2:54 am
Putting this in here as although its SQL 2000 based question, the relevent knowledge/experience will probably be in this forum...
I have a DTS package that does the following -
* Drops Replication Subscriptions.
* Calculates a table of records to delete, and pumps this to the other 2 servers.
* Deletes records on 3 Servers (Hundreds of thousands) based on the "deletions" table.
* Puts replication back in place.
Now the issue is that I need the final step to run, even if anything after the dropping of subscriptions fails.
This job runs overnight, and I cannot afford the system to be running without replication come the next day when we have sales being put through again.
Now if I run the 3 "deletion" stored procs one after the other I could have a failure workflow path heading off to adding the subscriptions back. But I need all 3 to run at once due to time constraints. Therefore I need the failure step to be followed if just 1 step fails, but not until the others have finished doing their stuff! Some kind of delay maybe?
An ideas on how I could do this or pointers are very much appreciated! And ay questions to clear up the description above...please ask! 😉
June 4, 2008 at 4:18 am
Crazy fool. I talked myself into not being able to use "On Completion" for the deletion steps....but it clearly works.
Thanks anyway, but if anyone has tips on scripting around events in DTS that'd be lovely.
Cheers
June 4, 2008 at 11:46 am
Are you going to be moving these jobs to SSIS anytime soon?
If you are, I would be interested in the workings thereof, as I havent really seen anything on this yet, and so far havent had the opportunity to focus on replication in SQL2005
~PD
June 4, 2008 at 4:56 pm
To be honest our project outlook means no 2005 migration until last quarter of this year but when we do I'll try and update this!
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply