Geek asks and answers

How to use the DontSaveSensitive and xml configuration file during the development of the SSIS package

Is it possible to install the SSIS ProtectionLevel package for DontSaveSensitive and use the connection string with the password from the configuration file during package development in Visual Studio ?

I have a package, for example. Package1 with ProtectionLevel = DontSaveSensitive . This package uses a connection from the connection manager, for example. Connection1 .

Package 1 includes configuration support using the file1.dtsConfig configuration file with the specified connection string. There is a password in this connection string:

<DTSConfiguration>
    <DTSConfigurationHeading>
        <DTSConfigurationFileInfo GeneratedBy="..." GeneratedFromPackageName="..." GeneratedFromPackageID="..." GeneratedDate="20.3.2013 12:08:27"/>
    </DTSConfigurationHeading>
    <Configuration ConfiguredType="Property" Path="\Package.Connections[Destination].Properties[ConnectionString]" ValueType="String">
        <ConfiguredValue>Data Source=.;Password=Password123;User ID=MyUser;Initial Catalog=Catalog;Provider=SQLNCLI10.1;Persist Security Info=True;Auto Translate=False;</ConfiguredValue>
    </Configuration>
</DTSConfiguration>

Now, when you open the connection from the connection manager in Visual Studio, the text field for the password remains empty and the package does not execute. Why wasn’t I using the password specified in the connection string in the file1.dtsConfig configuration file?

enter image description here

+5
source share
3 answers

Finally, we found a way to do this:

  • Change ProtectionLevel to DontSaveSensitive
  • Create a configuration file with a connection string
  • Manually edit this configuration file: add a password to the connection string if you are connecting to SQL Server authentication

SSIS Visual Studio. " " , .

+4

SSIS Config File runtime. Save my Password, SSIS . vald BIDS session, , , BIDS, Visual Studio compile, run time, connection string Config File.

MSDN ,

: , , , .

0

In this case also, when the package was installed first to use EncryptSensitiveWithUserKey, then changed to DontSaveSensitive -protection level. You must manually edit the .conmgr file and delete the DTS: Password element and put the password in the connection string, since the dee user was spelled correctly.

0
source

More articles:


All Articles