I had posted this original post on August 7, 2014. The original post contained

Step 3 below (in between the lines):

----------------------------------------------------------------------

3) Developers should make changes\modifications in their folder.

If developers decide to make changes\modifications in the Vendor's Folder than fine; just please be consistent. The DBAs need to know where to grab the latest, tested package for code review, test and deployment.

The DBAs would then move the tested package to the DBAs' test and production locations:

I:\SIS\SQLServer\SSISPackages\Test\PackageFolder (for TESTDBServer Packages)

I:\SIS\SQLServer\SSISPackages\Production\PackageFolder (for PRODBServer Packages)

----------------------------------------------------------------------

Now we are trying to implement Environments and Variables. Again, we are a small shop, trying to keep things simple and not using a source control system.

By using Environments and Variables, is there a need to have two directory locations (as stated in Step 3 above) one for test and production? Seems like we could have one directory location and control which environment (test or production) the package runs against via Environments, Variables and package parameters.

Where should the package parameters (which define the Environments and Variables) be changed? Should they be changed within Visual Studio and saved within the Solution? Or should they be changed within the Integration Services Catalogs (in SSMS) by right clicking the package and selecting Configure? Or should they be changed within the Job (in SSMS) by opening the Job Properties, selecting Steps Page, clicking Edit, and selecting the Configuration Tab?

Still wishing that there was one document to explain the deploying and implementation of SSIS Packages and Jobs: http://www.sqlservercentral.com/Forums/Topic1602521-2799-1.aspx

Thanks, Kevin