Sql Server维护计划任务&完成
我有一个如下所示的维护计划...
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 ...
导入数据和处理数据正在调用作业,而后处理是一个执行 Sql 任务。 如果导入数据或处理数据失败,它将转到下一个客户端导入数据...
导入数据和处理数据都是包含使用内置 SQL 日志记录提供程序的 SSIS 包的作业。
我对当前配置的期望是:
- 客户端 1 导入数据运行:失败 ->客户端2导入数据|成功处理数据
- 处理数据运行:失败->客户端2导入数据|成功后处理
- 后处理运行:完成 ->成功或失败->下一个客户端导入数据
但这不是我在日志中看到的内容...... 我看到几个客户端导入数据 SSIS 日志条目,然后是几个后处理日志条目,然后回到客户端导入数据!嗯!!
我做错了什么?我不认为客户端 1 导入数据的“成功”部分会开始,直到它......嗯......成功又完成!日志似乎表明不然......
我真的需要这些任务是连续的而不是并发的。这可能吗?
谢谢!
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!
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(2)
尝试在需要分组执行的任务周围放置一个序列容器。
Try placing a sequence container around tasks you need to execute in groups.
对我来说,解决方法最终是不使用内置的“执行 SQL Server 代理作业任务”,而是使用“执行 T-SQL 语句任务”并调用一个阻塞直到完成的存储过程...
甜蜜的成功:-)
并且...
For me the workaround ended up being NOT using the built-in "Execute SQL Server Agent Job Task" and instead using "Execute T-SQL Statement Task" and calling a stored procedure that blocked until completion...
Sweet success :-)
And...