blogs.conchango.com

I have spoken previously about indirect configurations and tried to convince everyone of how useful they are. I noticed something today concerning indirect configurations that quite surprised me. If you execute a package that uses an indirect configuration and the environment variable is not present you get the following warning: The ...

For reasons that I'll save until another post, I always deploy my packages as files rather than to SQL Server. In doing this I have derived a folder structure that I use in order to keep all my deployed packages and other files in the same place:...\Root\CheckpointFiles ...\Root\Configurations ...\Root\ErrorFiles ...\Root\Logs ...

By now alot of you will be familiar with Configurations right? I am using XML configuration files extensively in my current project - they're a method of affecting the way your package executes - the most common use is to store connection strings for connection managers. I have built my packages in such a way that ...

UPDATE: It turns out that in actual fact the workaround isn't nearly as severe as logging off. All you have to do is start a new command window. Thinking about it this kinda makes sense - I'm guessing that the command interpreter (cmd.exe) collects (for want of a better word) all the environment variables when it starts up. Thans to Stu Preston ...