All geek questions in one place

Using version control with SSIS packages (saving sensitive data)

We are working on a group of SSIS packages that we use using version control (SVN). We have three ways to store sensitive data in these packages:

  • don't store them at all
  • saving them using a user key
  • saving them with a password

However, each of these parameters is inconvenient when testing packages saved and committed by another developer. For each such package, credentials must be updated regardless of how sensitive data is stored.

Is there a better way to work with SSIS packages?

+3
source share
2 answers

, " ". , . , , , , . , , , .

+7

- , . , xml / , , "c:\SSISConfig". xml , . SSIS . , . prod, . "Dont save sensitive".

+3

Source: https://habr.com/ru/post/1745568/

More articles:


All Articles