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 |
|
kjmraohyd
Starting Member
34 Posts |
 Posted - 2006-06-22 : 01:45:13
|
| We have couple of packages with more than 30 connections for a DB migration project. Each package runs over night and fails in betweeen because of some small reasons like not allowed null etc..We fix this error and again run the whole package which takes lot of time for us.Is there a way to start executing this package from the failed TASK.TIAJaganmohan Rao |
|
|
nr
SQLTeam MVY
12543 Posts |
Posted - 2006-06-22 : 10:20:35
|
| Your problem is that you are trying to control everything from a dts package.You could get it to look at a table and only run things if a flag is set but it's much simpler to control it from a stored proc.First thing you need is to log the start and completion of the tasks to a table - this will help with monitoring and troubleshooting and development.You can then in the package or SP look at this table and only run the transfers which have not completed.You might find it easier to run the overnight transfers in a package as you have now (but with logging) then have an sp which just runs the transfers which have failed and allows you to run an individual one manually.A simple way to do this is to move all your transfers into sepaerate packagkes which are executed by the control package (I assume you want them to run concurrently otherwise get rid of the control package and run them all from an sp) then the sp can run induvidual ones by using dtsexec and getting the location from a table.==========================================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. |
 |
|
|
|
|
|
How to Start from a failed Task