We attempted to implement the Chapter 2 Framework from the Knight, Vermeen, Moss, Hackney book on SSIS 2008: Problem Design Solution. We see a couple of problem areas (at least) in our interpretation of the guidelines from the book.
1. We are attempting to have one connection string per server: dev/prod
2. We have set up environmental variables per server: dev/prod
3. We have set up XML Package Variables per server: dev/prod
4. We have set up System Variables per server in SQL Server: dev/prod
We've had to manually key in the common connection string to all packages on a server environment in the component properties area (control flow; not data flow--ok there)
Shouldn't the connection property find the connection that we've instantiated and provide us with a pull down to select it?
The components are un-editable after we select the common connection string, but they still run properly in our SQL Server Agent Job.
The dev server variable overlays the prod server variable information duringprod component editing
We are'nt sure if these problems are related.
Here is our package variable:
Here is our DTSconfig file; we have a few variations of this that we've tried.
View Complete Post