Conn Mgrs: Shared Project Level or Package Level with Project level parameters (SSIS 2012)

hello,

this question ssis 2012's configuration approaches.

1. project level shared connection managers

2. package level connection managers, populated project scoped parameters

could me understand pros , cons of above 2 connection manager configuration approaches?

for example, suppose have connection manager data warehouse audit database (say, "dwaudit") has the same packages in project. define project level shared connection manager or define project scoped parameter which points dwaudit database , have package level connection manager initialised project scoped parameter within each package. (project scoped parameter can be initialised ssis "environments")

i guess second approach better because @ development time, can change project parameter point different databases (dev,test, local etc) quick testing in ssis 2008 changing the variable sets connection string of connection manager.

alternatively, can use simple approach first approach if define "environments" within visual studio/ssdt 2012 , choose appropriate environment rather fiddling connection string.

your views appreciated.

thanks

hi james,

comparing first approach, agree second 1 better choice. since have several configuration environments, convenient use parameterized connection mangers , make use of solution configuration manager switch server environment freely @ design-time. that’s why second approach recommended.

now determine use parameterized connection mangers, better use project level parameterized connection managers because not keeps benefit of using configuration manager enable avoid creating same connection managers different packages.

after deploying packages ssisdb catalog, can create server environments , server variables use different server environments package execution.

regards,

---

mike yin
technet community support

SQL Server  >  SQL Server Integration Services