Sql Server Maintenance Plan Tasks & Completion
Posted
by Ben
on Stack Overflow
See other posts from Stack Overflow
or by Ben
Published on 2010-06-18T04:39:48Z
Indexed on
2010/06/18
4:43 UTC
Read the original article
Hit count: 364
Hi All,
I have a maintenance plan that looks like this...
Client 1 Import Data (Success) -> Process Data (Success) -> Post Process (Completion) -> Next Client
Client 2 Import Data (Success) -> Process Data (Success) -> Post Process (Completion) -> Next Client
Client N ...
Import Data and Process Data are calling jobs and Post Process is an Execute Sql task. If Import Data or Process Data Fail, it goes to the next client Import Data...
Both Import Data and Process Data are jobs that contain SSIS packages that are using the built-in SQL logging provider.
My expectation with the configuration as it stands is:
- Client 1 Import Data Runs: Failure -> Client 2 Import Data | Success Process Data
- Process Data Runs: Failure -> Client 2 Import Data | Success Post Process
- Post Process Runs: Completion -> Success or Failure -> Next Client Import Data
This isn't what I'm seeing in my logs though... I see several Client Import Data SSIS log entries, then several Post Process log entries, then back to Client Import Data! Arg!!
What am I doing wrong? I didn't think the "success" piece of Client 1 Import Data would kick off until it... well... succeeded aka finished! The logs seem to indicate otherwise though...
I really need these tasks to be consecutive not concurrent. Is this possible?
Thanks!
© Stack Overflow or respective owner