Hello.
From what I've read Configurations are the recommended way to pass
connectionstring info to a package.

I've tried this in two ways:
1) Directly populating the connectionstring property via an XML
configuration file.
2) Populating the value of a variable (via an XML configuration file) and
then assigning that to the connectionstring.

With both of these methods I'm getting the same problem: My password is
getting dropped.

This is a development package, and hadnt been deployed to a different
server. Also my package protection level is set to "DontSaveSensitive".

For info its an ODBC connection to an RDB database. I've written code to
test the connection string which confirms the blank password from the SSIS
end. Also the Rdb logs confirm this.

Any ideas...?

Hi Jason,

Thank you for your post.

From your description, my understanding of this issue is: You are
developing a SSIS package and you use the ODBC connection to connect to a
database. You can not see the password after you set the package protection
level to DontSaveSensitive. If I misunderstood your concern, please feel
free to let me know.

According to the SQL Books Online, when you use the Do not save sensitive
(DontSaveSensitive) protection level, sensitive information in the package
is not saved.

For all values, sensitive information is defined as:

1. The password part of a connection string. However, if you choose an
option that encrypts everything, the whole connection string will be
considered sensitive.

2. The task-generated XML nodes that are tagged as sensitive. The tagging
of XML nodes is controlled by Integration Services and cannot by changed by
users.

3. Any variable is marked as sensitive. The marking of variables is
controlled by Integration Services.

To see your password, please change the protection level to
EncryptAllWithPassword or other options.

Here is the article about the protection level:

Setting the Protection Level of Packages
http://msdn2.microsoft.com/en-us/library/ms141747.aspx

Hope this will be helpful!

Sincerely,

Wei Lu
Microsoft Online Community Support

==================================================

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.

==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

Sorry Wei,
Thanks for the reply, but I must have explained poorly.
I realise the "DontSaveSensitive" means that Passwords etc will be removed
from the package.
My problem is that I am using a configuration file to try and populate the
connectionstring (including password) at runtime, but the password is being
droped from the value set in the config file.
As far as I am aware, Config files are the recommended way to pass
connectionstrings to your package???


"Wei Lu" wrote:

Hi Jason,

Thank you for clarify this issue.

I would like to know are you using the Package configurations?

Also, please provide the detail steps you do with the intergration package
for me to troubleshoot.

I look forward your reply.

Sincerely,

Wei Lu
Microsoft Online Community Support

==================================================

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.

==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

"I would like to know are you using the Package configurations?"
Yes. I am using Package configuratins in an XML file. I have slelected the
"ConnectionString" property to be included in the Configuration. I then
manually edited the XML file to ensure that the Password was specified within
the file.

"Also, please provide the detail steps you do with the intergration package
for me to troubleshoot."
1.) Add a connection manager referencing an ODBC DSN for an Oracle RDB
database.
2) Add a dataflow task to the package.
3) Add Script Source to the Dataflow, with the following code:

Public Overrides Sub CreateNewOutputRows()

Dim conn As New
Odbc.OdbcConnection(Me.Connections.Connection.Conn ectionString)


conn.Open()
Dim sSql As String = "Select [Fieldnameslist] From Product_Changes"

Dim adap As New Odbc.OdbcDataAdapter(sSql, conn)
Dim ds As New DataSet
adap.Fill(ds)

For Each dr As DataRow In ds.Tables(0).Rows
ProductsBuffer.AddRow()
ProductsBuffer.CHANGEID = CUInt(dr("CHANGE_ID"))
[OtherFieldsHere]
Next
End Sub

4. Set the ProtectionLevel to "DontSaveSensitive"
5. Add a package configuration specifying the connectionmanager & its
connectionstring to be included.
6. Edit the XML to include the password value.

For information, I have also added a few lines of code to output the
connectionstring to a text file, just before it is used. The value in the XML
config file is correctly being read, except that the password if being left
out.

I hope this helps you to troubleshoot the issue.
Kind Regards,
Jason

Hi Jason,

Thank you for the update.

Since I do not have a oracle database, I can not re-pro this issue exactly.
I do some research and would like to provide some suggestion.

Would you please try to use OLE db connection for Oracle and check "save my
password"?

Also, when you use the package configurations, please include the password
section.

Sincerely,

Wei Lu
Microsoft Online Community Support

==================================================

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.

==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.