|
|
|
Forum Newbie
      
Group: General Forum Members
Last Login: Thursday, February 14, 2013 6:43 PM
Points: 4,
Visits: 36
|
|
I'm currently using a SQL server table to store the SSIS configuration settings for my packages. I haven't played with the XML option, but find it interesting. Could someone comment on some of the practical applications of using the XML configuration file approach instead of using a SQL server table?
EDIT: and what I mean is what the advantages of using XML config files that could not be done or be done better vs. using the SQL server table approach, in real world application.
Thanks!
|
|
|
|
|
Grasshopper
      
Group: General Forum Members
Last Login: Monday, April 01, 2013 8:50 AM
Points: 15,
Visits: 66
|
|
I have just completed DTS to SSIS conversion and the XML config file worked great for my application. It made deployment much easier that before.
|
|
|
|
|
Forum Newbie
      
Group: General Forum Members
Last Login: Friday, March 08, 2013 6:20 AM
Points: 1,
Visits: 15
|
|
I used to create packages as files on disk. And after development is completed I copy them to appropriate production directory.
When creating configuration file (CF below) the only option I see is to set package CF with particular path_name.
Is it possible to have package understand to work with CF located in the very same directory (along with package file) no matter what path was documented for CF?
Or is it possible to change configuration file path without rebuilding the package?
Thanks
Yuri Rubinov
|
|
|
|
|
SSC Rookie
      
Group: General Forum Members
Last Login: Friday, January 18, 2013 2:00 PM
Points: 35,
Visits: 163
|
|
You can place the package configuration file in any location. What is important is for you to select the appropriate configuration file during deployment and to ensure the file can be read.
Should the path of the configuration file be changed, then the package should be re-deployed using the configuration file in the new path.
|
|
|
|
|
Right there with Babe
      
Group: General Forum Members
Last Login: Thursday, May 16, 2013 9:41 AM
Points: 739,
Visits: 1,565
|
|
| I think I read some where that after adding a new environment variable that you have to reboot. Is that true?
|
|
|
|
|
SSC Rookie
      
Group: General Forum Members
Last Login: Friday, January 18, 2013 2:00 PM
Points: 35,
Visits: 163
|
|
David, if you create a new system environment variable, you may have to restart the system, but for a user environment variable, you may have to log off and log on again.
Cheers!
|
|
|
|
|
SSC Rookie
      
Group: General Forum Members
Last Login: Tuesday, February 12, 2013 9:20 AM
Points: 30,
Visits: 100
|
|
I personally LOVE using the XML format. One thing that I found cumbersome however, is viewing the XML. If you right click on the .dtsConfig file, choose to open it in Visual Studio Version selector, it gives you one looooong XML string.
Hold Ctrl, press K, then D, and VS auto formats the XML for you. This has saved countless hours of reformatting.
This small nicety makes a world of difference, and old developer friend of mine showed me that trick.
|
|
|
|
|
Mr or Mrs. 500
      
Group: General Forum Members
Last Login: Wednesday, May 15, 2013 5:54 PM
Points: 525,
Visits: 617
|
|
Thank you for the article and thank you to Mathew for the trick with Visual Studio shortcut. Very useful!
|
|
|
|
|
UDP Broadcaster
      
Group: General Forum Members
Last Login: 2 days ago @ 7:39 AM
Points: 1,448,
Visits: 755
|
|
zanoni.harris (5/14/2009) Could someone comment on some of the practical applications of using the XML configuration file approach instead of using a SQL server table?
...what I mean is what the advantages of using XML config files that could not be done or be done better vs. using the SQL server table approach, in real world application.
Like a previous poster I use an Environment Variable as the 'parent' package configuration which contains the details of the SQL Server database table in which the 'child' package configurations are stored. The only advantage I can think of for the XML file approach is that it is more intuitive, i.e. you can see immediately what values you are setting for the variables/connection strings within your package rather than having to ascertain the location/name of table and then query that table. The big disadvantage is security; by storing the configuration details in a table you can set very granular permissions to that table - important if the table holds connection strings to production environments.
Regards Lempster
|
|
|
|
|
Forum Newbie
      
Group: General Forum Members
Last Login: Thursday, February 14, 2013 6:43 PM
Points: 4,
Visits: 36
|
|
Great, thanks for the info Lempster. Also, great tip with the VS and viewing XML files Mathew.
Best,
Z
|
|
|
|