August 18, 2016 at 7:23 am
How do you deal with differences between developing on a workstation and preparing to deploy to a server? For example, In my environment, I have network drives that are located on the server, and they even have the same mappings on the server, but when I deploy a package to the server, I always have to change everything to UNC paths. This wouldn't be too bad, but in my organization we use winscp with a script to grab files from an SFTP site, and the scripts in winscp cannot have UNC paths in them. As such, I end up having to remap my winscp scripts to use c:\folder_to_use and end up having no end of trouble getting everything to run smoothly. Does anybody have any suggestions as to how I can make this process less painful?
August 18, 2016 at 7:55 am
You can use Project Parameters and Expressions to specify things like server names and network paths at runtime. The value of the parameter can be set from the job step that calls the SSIS package.
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
August 18, 2016 at 9:04 am
Steven.Grzybowski (8/18/2016)
How do you deal with differences between developing on a workstation and preparing to deploy to a server? For example, In my environment, I have network drives that are located on the server, and they even have the same mappings on the server, but when I deploy a package to the server, I always have to change everything to UNC paths. This wouldn't be too bad, but in my organization we use winscp with a script to grab files from an SFTP site, and the scripts in winscp cannot have UNC paths in them. As such, I end up having to remap my winscp scripts to use c:\folder_to_use and end up having no end of trouble getting everything to run smoothly. Does anybody have any suggestions as to how I can make this process less painful?
Use parameters and connections for all of this config information.
Set the default values for all of these to be 'development' values.
After deploying to a server, use SSIS 'Environments' to override these default values. There is a Stairways article here [/url]which talks about them in some detail.
If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.
August 18, 2016 at 9:07 am
Thank you. The environment settings in SSIS are great.
August 18, 2016 at 9:37 am
Steven.Grzybowski (8/18/2016)
Thank you. The environment settings in SSIS are great.
They are excellent, but at least a step away from greatness, IMO, because trying to script them out (along with project references) requires a Master's degree in computer forensics 🙂
If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply