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 |
|
ditch
Master Smack Fu Yak Hacker
1466 Posts |
 Posted - 2008-10-29 : 02:44:49
|
| Once an SSIS Package is in production, can it be restarted easily from a certain place in the package (so as to eliminate running parts that have already run)?Would it not be better to have the package broken up into smaller packages and contained in a job with multiple jobsteps, that way restarting from a point in time would be easily controlled by standby personnel and in some cases wouldn't even require having to open up a package?What are your thoughts on this?Duane. |
|
|
webfred
Master Smack Fu Yak Hacker
8781 Posts |
Posted - 2008-10-29 : 04:03:04
|
I would split my big packages in logical parts (packages) wherever it's possible and meaningful. It's a great help for Operators to have a point to restart when some disaster happened.Additional I would, whenever it's possible, do it without packages. That means for example to call a SP directly in the Job without having the overhead of a package.Webfred
No, you're never too old to Yak'n'Roll if you're too young to die. |
 |
|
|
rgombina
Constraint Violating Yak Guru
319 Posts |
Posted - 2008-10-29 : 07:11:29
|
| Read up on SSIS Checkpoints also and see if it gives additional benefit:http://blogs.conchango.com/jamiethomson/archive/2005/04/20/SSIS_3A00_-Checkpoint-clarification-_2D00_-Recovering-failed-packages.aspx |
|
|
|
|
|
|
Long running packages