August 9, 2016 at 9:04 am
Does anyone know of a global way in SSIS to prevent the validation/authentication of data connections/data flow tasks when simply opening an SSIS package?? I know I can change each data connection and each dataflow's "DelayValidation" property to be "True" (and to simplify this you can do a global search and replace on the actual .dtsx file itself within notepad) BUT I would prefer to set this in one place within SSIS if it exists. I have poked around and havent; found anything as of yet... (we are using SSIS version 2008)
We are using Oracle connections in SSIS and occasionally the Oracle account password needs to be changed that we are using in these SSIS db connections. When this occurs, opening an SSIS package immediately causes a validation attempt for each of the dataflows that are using the Oracle connection and after three invalid login attempts, this Oracle account gets locked out, which in turn causes all sorts of user issues and makes helpdesk a busy spot! I don;t have a problem using the above method of search and replace but I am sure I will forget at some point to do this and when I do, all heck will break loose!!!
Any advice/recommendations in this matter would be greatly appreciated!
Thanks, Brad
August 9, 2016 at 9:28 am
I think that the 'Work Offline' option on the 'SSIS' menu is the closest you can get to this. But as you've already done your homework, I suspect that you'll be familiar with this option.
The absence of evidence is not evidence of absence
- Martin Rees
The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
- Phil Parkin
August 10, 2016 at 1:59 pm
Yes, that is certainly an option (which I had forgotten about) for sure but can be an issue if you are opening a project that had one or more packages open from the last time. I know there is a workaround for that but likely you will open the solution and then remember there were open packages when it's too late!!! other than that it def a good solution. Thanks for reminding me!
August 10, 2016 at 2:26 pm
There is a DelayValidation property at the package level. Is that what you're looking for?
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
August 10, 2016 at 2:27 pm
brad.pears (8/10/2016)
Yes, that is certainly an option (which I had forgotten about) for sure but can be an issue if you are opening a project that had one or more packages open from the last time. I know there is a workaround for that but likely you will open the solution and then remember there were open packages when it's too late!!! other than that it def a good solution. Thanks for reminding me!
As you have alluded, you can delete the hidden .vs folder (should be in the same place as your .sln) before opening the solution, if you do not want to automatically re-open packages which were previously being worked on. Maybe there's a setting in the VS GUI that prevents this too, but I haven't seen it.
The absence of evidence is not evidence of absence
- Martin Rees
The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
- Phil Parkin
August 10, 2016 at 2:36 pm
Yup, I did see that... That's actually what I have been using, I modified the packages .dtsx files in notepad and did a global change to set that property to true. it works... I was just wondering if there was a nice easy setting somewhere - right in the SSIS data options would have been nice... Between the delayvalidation property and the work offline method, I'll be fine... Guess I'm just getting picky in my old age!!! LOL!
August 10, 2016 at 2:37 pm
No worries, I can manage...
August 10, 2016 at 2:59 pm
brad.pears (8/10/2016)
Yup, I did see that... That's actually what I have been using, I modified the packages .dtsx files in notepad and did a global change to set that property to true. it works... I was just wondering if there was a nice easy setting somewhere - right in the SSIS data options would have been nice... Between the delayvalidation property and the work offline method, I'll be fine... Guess I'm just getting picky in my old age!!! LOL!
If you set DelayValidation = False at the package level, then there should be no need to set it at the individual Data Flow or task level. Are you saying you wan to set it in one place the project level and have it take effect globally for all packages in that project?
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply