November 4, 2010 at 9:22 am
Ok on my current project I have configured package configuration for the 3 database conection strings that are used and can change.
These 3 are logged into a table on the destination database(so I got an InputDB1, an InputDB2 and an OutputDB).
Now I need to log any changes to these, since I've been told that when a configuration is unusable it uses its original setting.
Any help would be appreciated.
November 4, 2010 at 9:47 am
How are you determining if your configuration is usable or not? If you are trying to verify if a connection can be established or not, I would recommend using the following link:
Use the script task to determine if a connection can be aquired or not and then use constraint arrows after the script. If a connection is established use then set the current configuration as the one to use, otherwise use the old connection.
November 4, 2010 at 4:05 pm
checking if the connections are available is the priority
the script to loop through all connection managers will help with that
see my boss claims the following
let say you have a connection string to 'Adventureworks' (source db) and one to your own database 'YourDB' (dest db)
you keep the connection strings in a table on 'YourDB', using package configuration sql server
let say you change your connection string to 'Adventureworks2' which doesn't exist
somehow (according to my boss) it will revert bk to the original setting of 'Adventureworks'
November 6, 2010 at 1:02 pm
Resender (11/4/2010)
checking if the connections are available is the prioritythe script to loop through all connection managers will help with that
see my boss claims the following
let say you have a connection string to 'Adventureworks' (source db) and one to your own database 'YourDB' (dest db)
you keep the connection strings in a table on 'YourDB', using package configuration sql server
let say you change your connection string to 'Adventureworks2' which doesn't exist
somehow (according to my boss) it will revert bk to the original setting of 'Adventureworks'
That may work for variables configured through package configurations, but I believe that connections set through package configuration will fail upon validation if they are not valid. And that's a good thing. Otherwise some value typed in during development can travel along to production.
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply