If you put them as separate steps in a single job then they will execute one after another.
For any more complicated dependancies you will have to write a scheduler.
======================================
Cursors are useful if you don't know sql.
DTS can be used in a similar way.
Beer is not cold and it isn't fizzy.
>> Or use DTS, which handles such things with ease and grace.
Umm - easier than using sql server?
======================================
Cursors are useful if you don't know sql.
DTS can be used in a similar way.
Beer is not cold and it isn't fizzy.
The problem is the jobs are started from a polling application. This application is run every 5 minutes, and if it finds are certain flag-file, indicating an upload of source text files has completed, it starts the job belonging to that flag-file.
I have three types of flag-file and also three distinct jobs. If the sending party would send to different sets of data with their flag-files, the second job would start before the first one has finished. The second one should not start until the first one is finished.
I thought there might be a default switch somewhere that prevents two jobs from running simultaneously, like the "parallel processes" option in a DTS package.
I have a scheduler that does exactly this (and a lot more) after writing virtually the same thing for several companies.
It defines steps which will complete or re-schedule and have dependencies between steps and priority windows and alerts. Defaults to single threading but will multi thread on to a sum of defined step values.
It's pretty simple to write something like that and most batch processing systems need it.
I don't like separate flag files as it complicates things - prefer to import data from files whenever they arrive and check dependencies for future steps.
For importing and archiving any files that arrive see
======================================
Cursors are useful if you don't know sql.
DTS can be used in a similar way.
Beer is not cold and it isn't fizzy.
Problem with no using flag-files is you are never sure the upload to your inbox is complete (we get our files FTP-ed and this can take as long as 1 hour to complete). Also, if a transmission is aborted half way through a partial file could remain in the inbox. The sending party should reschedule and overwrite this file.
Perhaps there are easier ways, but flag-files seemed the quickest solution to these 2 problems.
Just adding it. It's just a list of some of the facilities available and scenarios.
Should be up this evening if I get round to it.
======================================
Cursors are useful if you don't know sql.
DTS can be used in a similar way.
Beer is not cold and it isn't fizzy.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.