SSIS package not using configuration from SQL server table
Hello all,
I have an issue with my SSIS package not using the package configuration specified in my SQL server table. This is a simple scenario where I need to move data from a csv file to a SQL server table.
I have 2 connection Managers - one for the location of CSV file and another for the SQL database connection string. I chose to Enable Package configuration. Two configurations -
a. Environment variable to store the database connection string.
b. SQL server table configuration for flat file connection manager.
The location of the CSV file is dynamic..so the idea is to change the path as and when needed in the SQL table.
No errors..everything works fine except that the properties of the flat file connection manager is not being pulled from the SQL server configuration table. It uses the location I had specified during design time.
How do I force the SSIS package to use the configuration specified in the SQL table always.
I've been spending a lot of time on this with no success. Please help..
Thanks
Karthik
Thats for your reply Rafael and John.
The configuration is in the same database as set in the env variable.
I am following the same instructions as in
http://rafael-salas.blogspot.com/2007/01/ssis-package-configurations-using-sql.html
This is procedure I followed for package configuration in that order-
1. SSIS --> Package configuration
2. Add --> Configuration type = Environment variable --> Choose the env variable I had created for DB connection --> From properties list choose connection string for the DB connection manager --> Give a name --> OK.
2. Add a second configration of type SQL server --> Choose Specify configuration settings directly --> Choose the db connection manager --> specify the configuration table --> Set configuration filter --> Next --> Choose all objects for configuration
Al I missing something here?
Thanks
Karthik
I've used both XML files and environment variables to set an initial connection for my SQL configs, and set the rest of my configurations from the SQL table. I've never had any problems with this approach.
Can you confirm that the enviroment variable configuration is the first item in your configuration dialog?