tiffanyjanetblack (9/23/2009)
yes, it appears I will have to manually change that ini file for deployment to each instanceon the SQLDEV box.
However, I am not sure that will solve my problem....once they are deployed and I
want to run them (via sql agent) how will the packages know that the connections
should point to the instance? LIke, I have a connection called "MDS", in the setting I had
to specify the server and instance and db(SQLDEV box, SQLDEV instance, MDS db).
As I said in the 1st posting, in previous life I had an environment variable ON the servers
for the MACHINENAME and was able to reference this in my package configs so It knew
which box to use (and subsequently which db).
The problem #2 is similar, but different.
THe staging packages pull data off the AS400 source system.
On my SQLDEV box I want to pull from the DEV AS400 (whose library name is "LANSADVL", box
name is "DVL").....but for production I want to read from MBM box with library name "MBM".
I dont see how I can achieve this without copying the staging packages and opening
each one and modifying the connections.
For #1, you might add a variable that is filled in by the job indicating what instance. Then in the package you evaluate the variable and adjust the servername as needed. This would allow a great deal of flexibility as to default instances or a named instance. I do understand about MACHINENAME, which unfortunately is not much use when named instances are in play..
For #2. Are these all properties of the connection for AS400, I have to ask because I don't have any experience in that particular tech.. Or are they part of the connection string.. Either way, you could do it either with the config file, or a combination of the config file and a script task. If these are all properties of the connection then you can select them individually in the PAckage Config wizrd and adjust them in the file. If not then you can pass the values in with the config file and assembly them using a script task, then assign the connection string to the connection right there in the script task..
CEWII