November 8, 2011 at 2:53 pm
I've been working on an ssis package. I have it all working just fine, last step has been to put the connection strings in a database. That works fine for all the control flow tasks, but the data flow task is not happy at all. I'm using a exec sql task to get the connection string out of the db, then using that to set the connection string property of the connection at runtime. Works just fine for control flow, but not for data flow. Am I doing something wrong? I sure hope I don't have to use a package config to do this as this company does not use those.
It looks like if I set ConnectionString in Expressions, that overrides the connection I want to use at design time. Not sure how to get around this.
Thanks!
.
November 8, 2011 at 3:37 pm
Use a variable for the ConnString that you use to overwrite the Expression.
Then set the variable to the appropriate environment at design time.
When you setup the job, you can specify a different value for that variable.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
November 8, 2011 at 3:43 pm
Thanks SQLRNNR. That's exactly the problem. I didn't realize when using an expression to set the connection string to a variable, that variable needed to be set at design time in addition to runtime.
.
November 8, 2011 at 3:49 pm
See if this article helps.
http://msdn.microsoft.com/en-us/library/ms141682.aspx
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply