CptCrusty1 (8/26/2013)
Steve Jones - SSC Editor (8/26/2013)
You could parameterize this path, so the package reads something from the local instance at runtime. That way if you have the local instance with the correct path, things work. I might even use a local table as you might have different paths for different packages.Parameterizing the path is an interesting idea. That would work for solutions moving forward. A local table would mean building structure across several servers. I don't "they" will like that one...
Can you outline how you'd parameterize the path?
In SSIS you create a variable that defines the path and file names. In the tasks, you then create an expression that uses the variables to generate the correct path name.
Once you have that working, you then create a package configuration where you have multiple options. You can store the configuration in an XML file, database, environment variables, etc...
For deployment, you build the package and create a deployment manifest. Using the deployment manifest on the destination - you can then specify where the package resides, the configuration to be placed, etc....
Here is a link to a tutorial for package deployment: http://technet.microsoft.com/en-us/library/ms365338.aspx
Jeffrey Williams
“We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”
― Charles R. Swindoll
How to post questions to get better answers faster
Managing Transaction Logs