September 28, 2016 at 6:33 am
We have been noticing some odd behavior in SSIS when adding / removing stuff from config files and we're wondering if anyone else can replicate this behavior.
This is what we're doing:
Open an SSIS package, right click in the white space, choose Package Configurations. Edit an existing one. Remove or add one thing, then go to the physical config file, open it up with NotePad, and suddenly everything except maybe the item you added is missing. As if all other settings in the config file have been removed.
This morning, I opened up a package with an existing config file, added a second config file because I wanted to compare something. We have 3 connection managers. I went in to add the connection string only for each of those, closed out of the Package Configuration Wizard, and only the last one that I chose was in the new file. So I opened it up again, expanded the properties for all three connection managers and started clicking "connection string" and watch as it moved my click to the next one instead of keeping it. And then had to go in and click the previous two after choosing the last one to get the checks to stick.
WTF?
Can anyone replicate this behavior? Does anyone know what's going on?
This is using SQL 2012 Data Tools (not the 2010 Data Tools that comes with SQL 2012).
October 1, 2016 at 6:05 pm
Hi
I tried this bit with the 2010 data tools that comes with ss2012.
Open an SSIS package, right click in the white space, choose Package Configurations. Edit an existing one. Remove or add one thing, then go to the physical config file, open it up with NotePad, and suddenly everything except maybe the item you added is missing. As if all other settings in the config file have been removed.
It worked ok for me, with no odd behaviour.
Regards
Phil
October 3, 2016 at 8:00 am
Well I just verified with a brand new package and a brand new config file that it's still happening. I narrowed down when it happens too. If I open the properties of one connection manager / variable, then click ConnectionString, then open the properties of the next connection manager / variable, it clears the initial check mark. So now I'm having to go open everything's properties before I check anything.
Once I do that, the check marks are sticking on the single property per item that I want in my config file.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply