SQL Server Integration Services Automation

  • Comments posted to this topic are about the item SQL Server Integration Services Automation

    Blog: Gulappa

  • unable to locate the automation file mentioned in the article

  • Can you put SP OthCalculateNextDate in separate box as ConCheckHoliday just to make it readable?

  • Yes, I can't find automation file mentioned in the article either, pls someone tell me where I can find the zip file.

    Thanks,

    Pyay

  • I don't understand, if this is a monthly process why not just schedule it to run every month?

  • It appears that the author did not include a link to the "Automation" zip folder that contains the dbscript.sql, SSIS package, and extract files.

    These would be helpfull in order to work through the examples in the article.

    Thanks

  • For all members:

    There are two issues need to be corrected by SSC team.

    1. I had provided automation.zip folder. SSC team has forgotten to upload the same. I will follow-up with SSC team to upload the file now.

    2. I will ask SSC team to store the SP OthCalculateNextDate in a separate box as ConCheckHoliday

    Thank you for your comments

    Blog: Gulappa

  • No such thing as a mistake - its called deployment testing....

  • Thanks for having SSC get the file attached to the article.

  • For all members:

    The enclosed two issued have been resolved by SSC team.

    1. Uploaded automation.zip folder.

    2. Store SP OthCalculateNextDate in a separate box

    You can use the example along with an article now.

    Blog: Gulappa

  • Thank you very much for your post - it coincidentally occurs at the same time as a major project that is very much an analog to it has been handed over to me for maintenance and execution. Your post will be my late night reading for the next few days. Thanks again - it was fortuitous to come across your posting. Mike 🙂

  • Because of this:

    The user requirement is described as follows:

    1. Client gets extracts from five different source systems (.txt, .csv and .xls file) every month on different weekdays.

  • Christopher West (10/30/2007)


    I don't understand, if this is a monthly process why not just schedule it to run every month?

    Because of this:

    The user requirement is described as follows:

    1. Client gets extracts from five different source systems (.txt, .csv and .xls file) every month on different weekdays.

  • The issues with the ZIP file were the editor's (my) fault. They have been corrected and my apologies.

  • It is a great article! :Wow:

    Thanks for sharing a bunch of knowledge.

    On my part, I would like to know that how much time the whole process took you to complete?

    I know that it depends upon many factors, but suppose you are ready with the requirement then what the time will be.

    I liked the way of scheduling, however this is the first time I have come across any job scheduling defined from database.

    Thanks.

Viewing 15 posts - 1 through 15 (of 17 total)

You must be logged in to reply to this topic. Login to reply