August 26, 2013 at 10:10 am
Our company has VM's that users access by remote access (RDP). This solution, even though the number of connections is limited, has been fine for many years. Now that the company has grown this presents a problem. I want developers to Test a Developer SSIS packages on their local desktops; however, if they create a connection to a flat file, they'll have to change the connection once they move it back to the VM since the paths to the flat files will change.
Example: I have a package I'll call "MoveData" that pulls flat files from a drive mapped as F: with the folder of "LOAD" this "F:\Load" is where the package gets it's flat files. We have literally hundreds of packages with multiple connections like this. Since there are limited connections to this VM (3 I think), I want developers to put the packages together on their local desktops; however, the path to the Flat will will be different.
Any way I can either set up a standardized drive mapping on the developer's computer that matches the UNC path on the VM, Or bulk Change all the Flat File mappings once the package is migrated back to the VM?
I can't change the VM. WAY too much effort involved.
Thanks
Crusty.
August 26, 2013 at 10:57 am
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.
August 26, 2013 at 11:26 am
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?
August 26, 2013 at 12:35 pm
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
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply