Post reply

Connection Manager not using the ConnectionString value

  • February 19, 2015 at 10:05 am

    #297855

    I have a child package where the ConnectionString property of a Connection Manager is set by a Parent Package Variable Configuration. I set up a script task that brings up a message box with the value of the ConnectionString property right before the dataflow task.

    MessageBox.Show(Dts.Connections["CPU_*"].ConnectionString.ToString());

    When I run the parent package, the message box shows that the connection string is changing with every iteration, but in the dataflow it always draws the data from the same source.

    The connection manager is an ADO.Net type, RetainSameConnection is set to False, and I've been researching this for days. Anybody have any ideas?

    (Update 2/23/2015): To make this stranger, when I look at the diagnostic logs, they tell me that when the new connections are being opened they are using the new connection strings.

  • February 23, 2015 at 1:56 am

    #1779199

    Assing connection string value to a Variable in Child package and try using that variable value as connection string to your connection using expressions.

    You can check below post which is doing somewhat similar task -

    http://blog.sqlauthority.com/2014/08/07/sql-server-ssis-parameters-in-parent-child-etl-architectures-notes-from-the-field-040/

    ____________________________________________________________

    AP

  • February 23, 2015 at 8:54 am

    #1779293

    I actually was doing that first and encountered the same problem.

Viewing 3 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply