Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2006-07-11 : 11:23:53
|
| Kur Lan writes "Hi Champs!I am developing a SQL 2005 datawarehous solution for a customer.I have come to the point where I now have several individual DTSX packages and can run them as jobs. Some jobs are depending on other jobs have sucessfully compleated, and some jobs not run at the same time as other jobs.My question is; is there a best practice or procedure, to manage, stear, and schedule the packages run in sql 2005? And what is the best way to monitor this execution production line?/Many Thanks" |
|
|
nr
SQLTeam MVY
12543 Posts |
Posted - 2006-07-11 : 11:51:49
|
| I often write a scheduler for this sort of thinghttp://www.nigelrivett.net/Products/Scheduler.htmlDepends how sophisticated you want to be.You could just have the job call an SP repeatedly which decides whether it can continue or wait.You can do a lot by putting dependencies in job steps, always logging completion to a table and checking that table from other jobs for other dependencies.==========================================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. |
 |
|
|
|
|
|
Managing running Packages and jobs