Post reply

How to schedule SSIS package (new 2012 deployment model)

  • February 29, 2016 at 11:18 am

    #324559

    How is it different in 2012 SSIS deployment model and package execution comparing to old package deployment model?

    Should I schedule each package through sql server agent?

  • February 29, 2016 at 11:33 am

    #1861891

    SQL!$@w$0ME (2/29/2016)

    How is it different in 2012 SSIS deployment model and package execution comparing to old package deployment model?

    Should I schedule each package through sql server agent?

    SQL Server Agent ... yes.

    Once you've selected that you want to run an Integration Services package, the rest should be obvious.

    One additional thing: if you are using SSISDB environments to control package params and connections, you will need to tell the package which environment to use.

  • February 29, 2016 at 12:24 pm

    #1861921

    One additional thing: if you are using SSISDB environments to control package params and connections, you will need to tell the package which environment to use. 

    Thanks.

    Should I set connection managers in sql server agent step properties?

  • February 29, 2016 at 12:41 pm

    #1861926

    SQL!$@w$0ME (2/29/2016)

    One additional thing: if you are using SSISDB environments to control package params and connections, you will need to tell the package which environment to use. 

    Thanks.

    Should I set connection managers in sql server agent step properties?

    If you want. But I'd use environments (same environment can be used for multiple projects, so when something (eg, a connection string) changes, you only need make the change in one place).

  • February 29, 2016 at 1:47 pm

    #1861960

    Thanks Phil!

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

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