SSIS 2012 Design : Project Deployment model

 

Hi ALL

i have question regarding SSIS 2012  deployment design .  we are using Project deployment model . we have everything in Project and Package parameters. we have created Environments and required Variables in those  environments .

Do we still need [SSIS Configurations] table to set the configurations ? what is the use old configuration method ,  can t we achieve this  with only Environment variables and Parameter combination ?   what are pros and cons of these 2 methods.

June 12th, 2014 6:03am

Project deployment plus package and project parameters gives much more feasibility than using  configuration(s) ...For your question why are they still there , Just to provide back ward compatibility and packages which are developed in SSIS 2008(R2) can still be upgraded and  ran on SSIS 2012 Integration Service using previous versions of  configuration things .

You are also allowed to use  both Configurations and Parameters in SSIS 2012 ..But to keep it clear and simple  I'd prefer package/Project parameters in SSIS 2012 managing everything via package parameters ignoring old configuration methodology !

Free Windows Admin Tool Kit Click here and download it now
June 12th, 2014 6:16am

Hi Surendra,

Its not supported to add package configurations when the SSIS Package job step references to a package stored in the SSISDB catalog database. So, it is recommended that you use parameters to implement the package configurations.

Regards,
Mike Yin

If you have any feedback on our support, please click here

June 18th, 2014 5:11am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics