title: SSIS - Package Configuration - Environment Variable
body: <p>Few things I would like to clear before I ask my main question.</p>
  
  <p>If you create more than 1 package (same source/destination), can you just use one Package Config file?</p>
  
  <p>->Lets say I have created 10 packages using same source/destination. Can I create just one XML package configuration and use that xml file to edit path for source &amp; destination? Or do I need to create 1 Package Configuration file per Package?</p>
  
  <p>Let's say you have 50 packages that you are moving to production server from development server...Where can I store the package configuration files in this scenario?</p>
  
  <p>->I have not created package configuration file for any package yet.</p>
  
  <p>->Should I create a SINGLE XML package configuration file for ALL 50 packages? </p>
  
  <p>->If not, what steps should I take?</p>
  
  <p>->I read that Environment Variable is a useful in this situation.</p>
  
  <p>-><strong>What steps do I need to take in order to create an Environment Variable?</strong> ELI5 if possible.</p>
  
  <p>->I read that it only allows one property to be stored...do i have to create multiple Environment Variables for lets say Source, Destination, credentials, etc?</p>
  
  <p>-> I read <a href="http://www.mssqltips.com/sqlservertip/1405/sql-server-integration-services-ssis-package-configuration/" rel="nofollow">this tutorial on Evn Var</a> but not understanding the procedure clearly and benefits of using Environment Variable for such situations (more than 1 packages, moving packages from one env to another, etc).</p>
  
  <p>Thank you kindly for your help. Try not to down-vote this post as I have done research but just not understanding it.</p>