Thanks for the series Andy.  I do have two questions though.  We are dealing with getting our DTS jobs under control.  Two things have surfaced just recently.  The first one is scheduling.  We have a lot of requirements for jobs that must run on odd-ball times.  For example, the last working day of the month, sixth to the last working day of the month, first working day of the month, etc.  Up to this point, we have had to programmatically handle this with a VBScript task in our DTS package.  It looks to a table and sees if the current date is in this table.  If so, then continue with package, otherwise stop running.

Management says this is good enough and is looking elsewhere for a scheduler like there is on the mainframe (yuck).  Do you have any suggestions?

Second question, has to do with DTS packages in general.  We have noticed that some of our packages show as a failed job, however we know that the package ran successful based on the outcome.  I haven't had time to investigate this, but my guess is that there is a VBScript task that is returning a controlled failure and for whatever reason DTS/Scheduler is picking this up and reporting the whole package as failed.  Have you seen this before?  If this is the case, then it would seem to me that you should be able to change the packages execution status.

Thanks and look forward to your upcoming topics.