Mike Dougherty-384281 (6/20/2012)
If the job fails to schedule its next occurrence then the job never runs again? So for quarterly jobs, you won't find out about the failure for at least 3 months and if it languishes in a broken state for as much as 6 months you could have serious consequences of a skipped job? (or adjust the timings for whatever interval; long or short it's a similar problem)
Nope, the emails tell you of successes and failures. In no way does this relieve you of your monitoring responsibility. All failures would require corrective action.
I would not want to be the person to inherit your role. Upon first-glance inspection at what is immediately visible, the jobs are all set to run once. There also exists some proprietary control tables that don't seem to be used in any business division. Until I dig into the package to discover the self-scheduling feature, it isn't obvious there even IS a schedule.
Really? you wouldn't want to open up a Sharepoint WorkGroup site with it all documented, the who, what, where, when etc? and then be able to go straight to the SSIS package, job history for review? Maybe you have been the victim of poor documentation. If you inherited my role, this would NOT be the case.... did i mention that it's all searchable too?
The proprietary control tables do exist in a lot of places, and educational institutions for certain have, and maintain these regularly.
I guess basically I'm curious why it's better to roll-your-own than to use the native scheduling feature that anyone educated in SQL Server would already understand.
This most definitely is NOT a replacement for scheduling but an 'addon' to handle cases where the native scheduling isn't as flexible as is necessary to the specific case at hand.