Using version control with SSIS packages (saving 'sensitive' data)
Posted
by sandesh247
on Stack Overflow
See other posts from Stack Overflow
or by sandesh247
Published on 2010-05-15T13:17:25Z
Indexed on
2010/05/15
13:24 UTC
Read the original article
Hit count: 294
Hi.
We are a team working on a bunch of SSIS packages, which we share using version control (SVN). We have three ways of saving sensitive data in these packages :
- not storing them at all
- storing them with a user key
- storing them with a password
However, each of these options is inconvenient while testing packages saved and committed by an other developer. For each such package, one has to update the credentials, no matter how the sensitive data was persisted.
Is there a better way to collaborate on SSIS packages?
© Stack Overflow or respective owner