June 11, 2014 at 2:50 pm
I have a package where I have configurations setting the connection managers info. The thing I've noticed is that the connection manager has the dev string in the connection string in the connection managers properties in VS 2008 and I deploy it that connection fails. I check the configuration table and its correct but when I open the package and update the connection string of the connection manager to the server where it shoould look after being deployed its fine. Isn't this what configs should allow me to avoid all together? Whats the use of using configurations if I still have to update the connection string in the package?
June 11, 2014 at 3:05 pm
There must have been some error somewhere.
Either the connection string in the configuration table is incorrect, or SSIS could not find the configuration table.
Do you have logging enabled in the package?
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
June 11, 2014 at 3:11 pm
I had an error in the connection string in my table. I was trying to import from one envoroment config table to another and then run updates. Guess the best way to set up the config table is to go through and update the connection strings with what is in the properties in VS after I get a passing connection test
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply