January 30, 2012 at 2:10 pm
HI,
What are your thoughts on using the package configurations vs the data source options? The data source options made sense to me because of the "single location to update". well now that I am deploying the package, it's a bit cumbersome, to keep the data sources pointed to the correct place for updating the code versus redeploying. I am thinking of using the package configuration options, but need some instruction on how to implement this. I understand the concept, but I don't get where the link from the config file (probably an XML file) to the connection manager is. I have 5 different data sources in a single package. Can anyone help?
Thanks!
Maggie
January 31, 2012 at 1:16 am
Go for package configurations, definately. Data sources are a Visual Studio thing and are not deployed to the server! (at least not in SSIS. It does work for SSAS and SSRS)
The XML file contains the connection strings for 5 connection managers, but first you need to tell the package where to find the XML file. You can do this by hardcoding the filepath of the XML file in the package (direct configuration), or by using an environment variable that points to the location of the XML file (which can change from machine to machine). This is an indirect configuration.
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply