Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 288
  • Last Modified:

SSIS restartability methods

Hi guys

Quesiton:  Has anyone built an SSIS feed that handles restartabilty at the previous run's point of failure?

I have an SSIS package I'm working that has 100+ data flow tasks, 50+ for salesforce.com to SQL staging tables, and then 50+ from those SQL staging tables to SQL destination tables.  I'd like to add restartability to this package, meaning if the feed fails at 2am at step 42, then when it's re-run at 3am it starts with data pump 42 and not 1.

I'm currently table-logging both the execution as one row in table ETL_PACKAGE_LOG, and each of the 100+ steps as one row in ETL_PACKAGE_STEP_LOG, so I can create a SQL task to determine the previous step that the package failed.

I don't need help with the SQL Agent 'How to restart a package if it fails' part of this question, just the how to handle it in SSIS.

Rather then build from scratch I though I'd ask here.

Thanks in advance.
Jim
0
Jim Horn
Asked:
Jim Horn
  • 3
3 Solutions
 
lcohanDatabase AnalystCommented:
I did similar things by grouping tasks in "sequence containers" inside SSIS and use "Precedence Constraints" in workflow/decision making based on output.

http://msdn.microsoft.com/en-us/library/ms141261.aspx

"Precedence constraints link executables, containers, and tasks in packages in a control flow, and specify conditions that determine whether executables run. An executable can be a For Loop, Foreach Loop, or Sequence container; a task; or an event handler. Event handlers also use precedence constraints to link their executables into a control flow. "

For example:
http://www.phpring.com/sequence-container-in-ssis/
http://msdn.microsoft.com/en-us/library/ms139855.aspx


There are loop containers as well:
https://www.simple-talk.com/sql/ssis/ssis-basics-introducing-the-foreach-loop-container/
0
 
Jim HornMicrosoft SQL Server Developer, Architect, and AuthorAuthor Commented:
Can you speak specifically to the question?  I'm not real big on 'here's a bunch of links, you figure it out' comments.

And I'm currently using containers around every task, and writing  begin_dt, end_dt, rows_source, rows_inserted, rows_updated, etc.  to my ETL_PACKAGE_STEP_LOG table.
0
 
lcohanDatabase AnalystCommented:
You can use "expressions" on the "precedence constraints" based on the ETL_PACKAGE_STEP_LOG table to determine if a sequence container should be executed or not. So let's say your SSIS started from SQL Job failed at 2AM and you put a retry on the job step or leave it for next run at 3AM when your SSIS will get the "expression" value (Run or do Not Run) based on the log table from the previous execution of that particular container/step. Hope this makes sense.
0
 
lcohanDatabase AnalystCommented:
"...if the feed fails..." - you could also use that log table (but this means more work indeed) to write a SQL query  (rather than default source table destination table SSIS data task) to transfer the data or not based on what was lastly logged for that particular task based on success/failure in the log.
0
 
Alpesh PatelAssistant ConsultantCommented:
Hi,

In that case you can use SSIS checkpoint file feature.

When your process fails. In next run It will start from the point where it was failed.
0

Featured Post

Learn Veeam advantages over legacy backup

Every day, more and more legacy backup customers switch to Veeam. Technologies designed for the client-server era cannot restore any IT service running in the hybrid cloud within seconds. Learn top Veeam advantages over legacy backup and get Veeam for the price of your renewal

  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now