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.