August 7, 2018 at 8:47 am
This is a 2-part question:
1) It is my understanding that we use XML Configuration file to store configurable values that could be used in your package without altering the package.
However, as you can see on screenshot 1, the Configuration String (path to the XML file) is hard-coded and has to be edited if the package is moved to a different server
where the path to the package and to the dtsConfig file is different. I may not understand something simple, but does it violate the whole purpose of moving package between the environments 'without altering the package' ?
In order for the xml configuration file to be used on a different server I have to edit (or create new entry/ADD) this path and re-save the package? Is my understanding correct?
Is there a way not to have to edit the Configuration String in SSIS->Configurations when moving package to Production?
2) When I press EDIT button I am getting the error message shown in the second attached screenshot. Does it mean it is not editable, and i need to Remove+Add new record for new path to .dtsConfig file?
Thank you.
Likes to play Chess
August 7, 2018 at 9:14 am
It's been a long time since I worked with SSIS, but we actually used a table/view to do our configurations. The table had a field for server name and the view filtered the field server_name = @@SERVERNAME. This allowed us to use the same table in all environments, but the results of the view would be appropriate for the deployed environment.
It's been so long, I don't really remember much more than that.
Drew
J. Drew Allen
Business Intelligence Analyst
Philadelphia, PA
August 7, 2018 at 1:08 pm
VoldemarG - Tuesday, August 7, 2018 8:47 AMThis is a 2-part question:
1) It is my understanding that we use XML Configuration file to store configurable values that could be used in your package without altering the package.
However, as you can see on screenshot 1, the Configuration String (path to the XML file) is hard-coded and has to be edited if the package is moved to a different server
where the path to the package and to the dtsConfig file is different. I may not understand something simple, but does it violate the whole purpose of moving package between the environments 'without altering the package' ?
In order for the xml configuration file to be used on a different server I have to edit (or create new entry/ADD) this path and re-save the package? Is my understanding correct?
Is there a way not to have to edit the Configuration String in SSIS->Configurations when moving package to Production?
2) When I press EDIT button I am getting the error message shown in the second attached screenshot. Does it mean it is not editable, and i need to Remove+Add new record for new path to .dtsConfig file?Thank you.
I've always used table-based configurations, with the connection string to the database containing the table as an environment variable, so I don't know for sure, either....
Steve (aka sgmunson) 🙂 🙂 🙂
Rent Servers for Income (picks and shovels strategy)
August 9, 2018 at 9:53 am
If you deploy your packages to SSISDB, this problem goes away, because you can do all of your config work with SSISDB 'environments'.
The absence of evidence is not evidence of absence.
Martin Rees
You can lead a horse to water, but a pencil must be lead.
Stan Laurel
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply