July 26, 2007 at 9:36 am
Hi
What is the main advantage in using environment variables when it comes to package configuration files? What I'm doing is:
Building and testing a package on a dev box with flat file and OLEBD connections.
Deploying that package to SQL Server MSDB on a live box.
Generating an XML configuration file from within BIDS on the dev box. Copying that file to the live box and editing it to point to the live database and flat files.
Using SSMS to schedule the SSIS package and on the configuration tab pointing to the XML configuration file.
This seems to work fine and doesn't require me to have standard configuration paths on all my boxes as I can specify the location when scheduling the job (e.g my dev pc doesn't have a d drive whilst my live boxes do)
So is there any advantage to introducing an extra step and having an environment variable that tells SSMS where the config files are located?
cheers
July 26, 2007 at 10:54 am
That's the way to do it. Have a environment variable which tells SSIS where your config files are. That way, deploying a package to a server is simply copying it over. Config file location is obtained from the variable.
Cheers,CrispinI can't die, there are too many people who still have to meet me!It's not a bug, SQL just misunderstood me!
August 17, 2007 at 2:20 pm
Hello,
I am new in SSIS.
Could you tell me how to explain how to create a environment variable which tells SSIS where your config files are.
Config file is already done.
Thank
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply