May 8, 2014 at 11:22 am
I was updating a package today and noticed that the ssis package has an SSIS variable holding the connection string for the OLEDB connection manager. The connection Mgr sets its connection string to the variables value in an expression. The DataSource for the connection string in the variable is hardcoded as "localhost". Am I assuming correctly that this will point to the databases on the server that the package is deployed to? The connection is used to point to the SSIS_Configurations table where the rest of the package configurations are held.
I would think that the best practice would be to create an enviroment variable on each machine (Dev, QA, UAT, and Prod) and set all connection Mgrs to use the enviroment variable as its connection string with an enviroment variable config. What do you guys think?
May 8, 2014 at 11:25 am
dndaughtery (5/8/2014)
I would think that the best practice would be to create an enviroment variable on each machine (Dev, QA, UAT, and Prod) and set all connection Mgrs to use the enviroment variable as its connection string with an enviroment variable config. What do you guys think?
I would strongly support the environment variable approach. This will make your life a lot easier when deploying to the environments you mentioned.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply