Post reply

Starting Point For SSIS Package Template

  • September 20, 2011 at 2:20 pm

    #257758

    I am investigating creating an SSIS package template for our organization. What is a good starting point? Creating a template with variables and a connection to the configuration database? Include logging/custom logging and error-handling? Error-handling would be on the entire package, right?

    Any guidance on this topic would be greatly appreciated. I know how to create the package template. I am just wondering about the components/tasks that I need to put in the package template.

    Thanks...Chris

  • September 20, 2011 at 2:41 pm

    #1384171

    The template package that we use contains;

    - a number of variables that are used for logging and error handling

    - an initial execute sql task that logs the start of the package to an audit table

    - a final execute sql task that logs the completion of the package and any errors associated with it

    -A generic container that holds the data flow that has error handling attached to it with a send email task setup

    -Error handling on the whole package that logs to and error table

    -A smtp connection

    so all we have to do when creating a new package is create the dataflow and set the emailto and emailfrom variables to have a complete package.

    Overall this works well and has cut development time

  • September 20, 2011 at 8:25 pm

    #1384299

    Thanks, SteveB.

  • September 25, 2011 at 10:37 pm

    #1386275

    Wonderful Steve.

    Raunak J

  • September 26, 2011 at 12:53 am

    #1386291

    steveb. (9/20/2011)

    The template package that we use contains;

    - a number of variables that are used for logging and error handling

    - an initial execute sql task that logs the start of the package to an audit table

    - a final execute sql task that logs the completion of the package and any errors associated with it

    -A generic container that holds the data flow that has error handling attached to it with a send email task setup

    -Error handling on the whole package that logs to and error table

    -A smtp connection

    so all we have to do when creating a new package is create the dataflow and set the emailto and emailfrom variables to have a complete package.

    Overall this works well and has cut development time

    I have about the same. I have also a connection manager to the configuration table, and usually a connection manager to the log database and optionally one for the MSDB database (for executing child packages).

    Need an answer? No, you need a question
    My blog at https://sqlkover.com.
    MCSE Business Intelligence - Microsoft Data Platform MVP

  • September 26, 2011 at 5:45 am

    #1386395

    Thanks, guys.

Viewing 6 posts - 1 through 5 (of 5 total)

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