We're saving our SSIS packages in Visual SourceSafe (VSS). When we develop them, things work fine, but then we have bizarre connection & error issues when someone checks the package out to edit. The default protection level on SSIS is "SaveSensitive With UserKey", or at least it is on ours. We figured out this was what was causing our so-called "package may be corrupt" errors and changed the protection leves to "Don't Save Sensitive".
Now, however, we can't use the SQL Server logins we use to connect to the DB with the Save Password option. When trying to debug the package, it says it can't connect to the server, but when we edit the connection and re-enter the password, the connection test goes fine.
DOH!
I looked for an Expression in the connection manager properties that would allow us to use a variable for a User Password, but found nothing. Any thoughts on this issue?
Thanks,
Catadmin - MCDBA, MCSA
"No, no. Yes. No, I tried that. Yes, both ways. No, I don't know. No again. Are there any more questions?"
-- Xena, "Been There, Done That"
Now, however, we can't use the SQL Server logins we use to connect to the DB with the Save Password option. When trying to debug the package, it says it can't connect to the server, but when we edit the connection and re-enter the password, the connection test goes fine.
DOH!
I looked for an Expression in the connection manager properties that would allow us to use a variable for a User Password, but found nothing. Any thoughts on this issue?
Thanks,
Catadmin - MCDBA, MCSA
"No, no. Yes. No, I tried that. Yes, both ways. No, I don't know. No again. Are there any more questions?"
-- Xena, "Been There, Done That"