Comments on RDA BI/SQL Server Practice Group Blog: Errors locating SSIS XML package configuration fil...

Jim, I was refering project real and taking this a...

2010-07-30T04:20:56.862-04:00

Jim, I was refering project real and taking this approach only. But Our DBA has concerns just keepintg a cmd/bat file and scheduling it. He sees security issues on that. Now i am trying to get the path to xml config file from a package variable.

Yes, Bob, as I stated in the conclusion, "hav...

2010-04-12T15:43:16.053-04:00

Yes, Bob, as I stated in the conclusion, "having a fixed configuration location or using an environment variable to hard-code the location of configuration files would avoid this situation, but places requirements on server configuration and directory structure." In companies where the developers have a fair amount of control over the servers, this is a good way to go. However, at some companies, the developers are not the individuals responsible for the servers, and when solutions get migrated from one server to another, those file paths and/or environment variables would have to be created on the new server. The client where I developed this approach had exactly this issue, and as a result, required that all solution files reside in a single location, and this approach worked to meet that requirement. Thanks for your thoughts.

Interesting article. Why not use an existing ENVVA...

2010-03-18T10:35:02.591-04:00

Interesting article. Why not use an existing ENVVAR, like, for example %SystemRoot%?

Then, put a root XML file there to point to a configuration table.

Set your Package Configuration to use an Indirect XML, point to a new ENVAR that uses the
%SystemRoot% ENVAR and a new file name (say SSIS_Config.xml), and finally set up a configuration table in the System Database on SQL Server.

Problem solved, no?