Comments on: SSIS 2012 “Cancelled” Status Issues http://thinknook.com/ssis-2012-cancelled-status-issues-2012-07-29/?utm_source=rss&utm_medium=rss&utm_campaign=ssis-2012-cancelled-status-issues Because the world needs another Business Intelligence blog! Fri, 14 Sep 2018 19:30:18 +0000 hourly 1 https://wordpress.org/?v=4.1.41 By: Jenn S. http://thinknook.com/ssis-2012-cancelled-status-issues-2012-07-29/#comment-2726 Mon, 29 Jul 2013 21:05:00 +0000 http://thinknook.com/?p=652#comment-2726 Awesome, yeah those indexes were definitely needed too. Thanks again!

]]> By: Links Naji http://thinknook.com/ssis-2012-cancelled-status-issues-2012-07-29/#comment-2691 Fri, 26 Jul 2013 21:48:25 +0000 http://thinknook.com/?p=652#comment-2691 Hey Jenn,

Awesome! am really glad this helped you. The SSIS catalog maintenance operation is definitely not thought out properly for a high usage environment.

I also recommend reading this nice article by Phil Brammer on how to optimize the SSIS catalog , which also speeds up the overall time it takes to complete the SSIS maintenance operation.

]]> By: Jenn S http://thinknook.com/ssis-2012-cancelled-status-issues-2012-07-29/#comment-2688 Fri, 26 Jul 2013 20:07:08 +0000 http://thinknook.com/?p=652#comment-2688 Thanks for this. What a lifesaver! After having our SSIS 2012 server in production for a year, we suddenly started seeing mass cancellations from midnight to 3 AM every night. Turns out that nasty SSIS Maintenance Job is configured to retain 365 days of data by default. So while it completed in a few seconds for the first year, it suddenly started to take three hours without warning, canceling everything in its path and leaving no useful error messages behind. What a mess! And incredibly inefficient just for maintaining ~100 rows!

We changed that job’s schedule and gave it its own time slot with no other competing packages, and all is well again.

]]>