March 9, 2009 at 2:02 pm
I have a solution with about 60 packages. There are four connections that may be used by the various packages (each package uses only two connections). Anyway, I have created four configuration files (one for each connection) and then I've gone through each package and setup the package configurations to use the proper config files. So far so good, everything works just fine
...until...
Now we have more than one person working on these packages so when we check the packages out of our source control system to his local drive and attempt to open any of the packages, we get a "cannot find the configuration file" error. The files are there but for some reason, SSIS can't seem to read them on his machine.
We can go through each package and delete the package configurations and add them again and now it works, but then if he checks the package in and I update from source control, now I have the problem.
I almost forgot to mention that we are using a relative path to the config files so instead of C:\SSIS\ProjectName\ConfigFileName.dtsConfig we use .\ConfigFileName.dtsConfig so that as long as the config files reside in the same directory as the package we don't have to worry about the path.
How do you set up config files so that you can work in a collaborative development environment?
Thanks.
/*****************
If most people are not willing to see the difficulty, this is mainly because, consciously or unconsciously, they assume that it will be they who will settle these questions for the others, and because they are convinced of their own capacity to do this. -Friedrich August von Hayek
*****************/
March 10, 2009 at 1:49 pm
I can't be the only one who's seen this problem can I?
/*****************
If most people are not willing to see the difficulty, this is mainly because, consciously or unconsciously, they assume that it will be they who will settle these questions for the others, and because they are convinced of their own capacity to do this. -Friedrich August von Hayek
*****************/
March 10, 2009 at 4:11 pm
No your not but nobody talks about it much.
I had the same problem. I referenced Project Real and made my own system off of that design.
Works pretty good, but appear cumbersome until you get your head around it.
What we now have is the ability for anyone to check out and work on a package then deploy it back to the server without any config changes (assuming the work that was done didn't impact the configs)
if the developer works on it it uses the dev database if it's in Q/A then it uses the Q/A database and when deployed to production it uses the production database.
check out this post it goes over my solution.
http://www.sqlservercentral.com/Forums/Topic666802-148-1.aspx
let me know if you have any questions.
- Tom
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply