I would use a variable for the ConnectionString property of the connection manager. A package level configuration can be very useful for accomplishing this task. Several ways to do this. I prefer to use a table in SQL Server that holds all the configurations for all packages. This can be especially effective if you have multiple packages and need to dynamically change a set of connection managers across those multiple packages.
The basic steps are:
- Opposite click on your SSIS design surface and select "Package Configurations..."
- Create a package level configuration of Configuration Type "SQL Server"
- Store your connection in a Configuration table in SQL Server
- Alter your Connection Manager to use a variable for the ConnectionString Property
- Populate that variable from the Configuration table via your package level configuration
- When it comes time to switch from Test to Production, simply update the connection string in your configuration table
These screenshots can help...
This is part of a larger package management framework that I implemented using this book:
Microsoft SQL Server 2008 Integration Services: Problem, Design, Solution
I highly recommend it. Should take less than a day to set it up. Book has step by step instructions.