November 20, 2007 at 7:07 am
Ok I give and this is a very stupid problem. I have to connect to a DB2 server to get 12 datasets. Each month I am forced to change the DB2 password. If I try to edit the package after a password change, SSIS blows up my password on DB2 (3 strikes & you're out) because the 12 source adaptors try to validate just because I opened up the package for editing. I don't even get a chance to let it know what the new password is! This is going to be total chaos after we get up to a dozen or so packages. The only recovery at this point is to leave it open, call my help desk and get the password reset/changed and put the new one into the connection manger so it stops throwing a snit. What a dumb#$@% set up. How do I tell SSIS to NOT try the connection till I tell it to run? That would be the common sense methodology and default but obviously not what it does.
I've tried the DelayValidation property on it and that doesn't work and I didn't find an obvious solution in Haselden's book.
Help
November 26, 2007 at 11:00 am
jere42 (11/20/2007)
What a dumb#$@% set up.
No argument there. But its your setup.
2 options.
1. Set BIDS to 'Work Offline' (its on the SSIS menu)
2. Set up your package to use a configuration (which you should be doing anyway) and change the password in the configuration prior to opening the package.
Regards
Jamie Thomson
Jamie Thomson
http://sqlblog.com/blogs/jamie_thomson
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply