October 28, 2009 at 2:22 pm
Hi pals,
We have development server and production server.
What is the best way to save the connection strings(data sources).
When I deploy to the prod server, I dont need to change the connection strings.
And quick question, what is the importance of shared data source as we are creating the connection for every individual package(add new datasource from existing).
Also we can change the properties once we added the datasource to a package even though it is a shared data source. What is the meaning of shared data source if we are not able to directly use in the package?
thanks in advance
October 28, 2009 at 2:29 pm
We use SSISConfigDB to store the connection strings.
November 27, 2009 at 8:29 am
Hi
What I have found useful is:
1 Envirionment Variable containing the path to the default configfile on every machine.
Ex. K:\SQL\Confiurations\DefaultConfig.XML
In that file you put the connectionsstrings and default paths to where the packages are (if you are using filebased deployment)
Then you add a package environmentvariable pointing to your Envirionment Variable in your SSIS - packages.
In that way you just have to move the package between the environments.
It kan be a little bit tricky if you are not allowed to have the password in an XML-file.
/Michael
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply