Sql Job运行30分钟然后报告成功
我们有一个每天晚上运行并在客户数据库上重建索引的作业，但是安装该作业后，根据历史记录，它每天晚上都成功运行，并且每天晚上大约 30 分钟完成，但是我们发现它应该的索引修复，实际上并没有修复，并且仍然碎片化超过允许的水平。
有什么因素会阻止作业运行超过 30 分钟吗？目前还没有结束日期。
We have a job that runs every night and rebuild the indexes on a customer database, however after installing the job, it runs successfully every night according to the history and finishes in around 30 minutes every night, however we found that the indexes that it should fix, are not actually fixed and still fragmented above the allowed level.
Is there anything that would stop a job from running more then 30 minutes? It currently doesn't have an end date on it.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
结束日期是指计划（用于确定何时开始工作）应停止有效的时间。 Sql Server 代理属性中有一个关闭超时设置，但默认为 15 秒，并且是关于完成关闭，而不是总执行时间。
那么...
您手动运行脚本了吗？
需要多长时间才能完成？
是否按照您的标准成功完成？
相关：
The end date is about when a schedule (for determining when to start the job) should cease to be valid. There is a Shutdown Timeout setting in Sql Server Agent Properties, but that defaults to 15 seconds, and is about completing shutdown, rather than total execution time.
So...
Have you run the script manually?
How long does it take to complete?
Does it complete successfully according to your standards?
Related: