Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Drive mapping Between VM and Local Desktop -Tricky Issue to work around.


Drive mapping Between VM and Local Desktop -Tricky Issue to work around.

Author
Message
CptCrusty1
CptCrusty1
SSC Veteran
SSC Veteran (226 reputation)SSC Veteran (226 reputation)SSC Veteran (226 reputation)SSC Veteran (226 reputation)SSC Veteran (226 reputation)SSC Veteran (226 reputation)SSC Veteran (226 reputation)SSC Veteran (226 reputation)

Group: General Forum Members
Points: 226 Visits: 387
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.
Steve Jones
Steve Jones
SSC-Dedicated
SSC-Dedicated (36K reputation)SSC-Dedicated (36K reputation)SSC-Dedicated (36K reputation)SSC-Dedicated (36K reputation)SSC-Dedicated (36K reputation)SSC-Dedicated (36K reputation)SSC-Dedicated (36K reputation)SSC-Dedicated (36K reputation)

Group: Administrators
Points: 36471 Visits: 18764
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.

Follow me on Twitter: @way0utwest
Forum Etiquette: How to post data/code on a forum to get the best help
My Blog: www.voiceofthedba.com
CptCrusty1
CptCrusty1
SSC Veteran
SSC Veteran (226 reputation)SSC Veteran (226 reputation)SSC Veteran (226 reputation)SSC Veteran (226 reputation)SSC Veteran (226 reputation)SSC Veteran (226 reputation)SSC Veteran (226 reputation)SSC Veteran (226 reputation)

Group: General Forum Members
Points: 226 Visits: 387
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?
Jeffrey Williams 3188
Jeffrey Williams 3188
SSCarpal Tunnel
SSCarpal Tunnel (4.5K reputation)SSCarpal Tunnel (4.5K reputation)SSCarpal Tunnel (4.5K reputation)SSCarpal Tunnel (4.5K reputation)SSCarpal Tunnel (4.5K reputation)SSCarpal Tunnel (4.5K reputation)SSCarpal Tunnel (4.5K reputation)SSCarpal Tunnel (4.5K reputation)

Group: General Forum Members
Points: 4468 Visits: 9836
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
Problems are opportunities brilliantly disguised as insurmountable obstacles.

How to post questions to get better answers faster
Managing Transaction Logs

Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search