Hello Lalitha,
Sounds like you have been reading my blog on WordPress concerning SSIS
Configurations.
What you are going to need is a system variable available inside SSIS that
is specific to each INSTANCE, and unfortunately, I don't see one. So you may
have to eliminate the dtsConfig file altogether and go with a hard-coded
connection to the SSIS Config database. BUT, when you deploy a package to the
Production Server and set it to run, you will have to set the SQL Agent Job
(or what ever method you use to invoke the ssis execution) to override the
connection string of that SSIS Config database, having it point to the proper
server/instance.
I feel for you on this one. There is no good reason to host TWO environments
on ONE machine, and a plethora of reasons NOT to.
Good luck.

Signature
=====
Todd C
> Hi,
> We have many SSIS Packages. All the connections/filepaths are
[quoted text clipped - 24 lines]
> Thanks,
> Lalitha
Lalitha - 02 Jul 2009 08:01 GMT
Hi Todd,
Thanks for the response. Yes I did read your blog on SSIS Configurations and
it was very helpful...
Regarding your suggestion to provide dtsConfig file path during run time in
SQL Agent, I did try that approach as well.. But I was having issues because
the child packages invoked from a parent ssis package were not able to
retrieve the path provided in SQL Agent.
May be I have to redesign packages to have global variable and provide
dtsConfig path through SQL Agent to the globa variable. This way child
packages may be able to fetch them.. But involves lot of rework now :-(
Thank you,
Lalitha
> Hello Lalitha,
> Sounds like you have been reading my blog on WordPress concerning SSIS
[quoted text clipped - 42 lines]
> > Thanks,
> > Lalitha
Todd C - 02 Jul 2009 13:41 GMT
You could use the Parent Package Variable as a way to assign values in the
Configuration of Child Packages. Once the Parent has the location (Connection
String) of the SSIS Config Db, it can pass that along to the children. You
could even pass along the Connection Strings of any and all Connection
Managers used in the children.
On a purist note, this is prefered over having each child go to the XML
file/SSIS Config Db to get the info, because it reduces round-trips to the
server.
But yes, it involves re-work. No way around that.
=====
Todd C
> Hi Todd,
> Thanks for the response. Yes I did read your blog on SSIS Configurations and
[quoted text clipped - 57 lines]
> > > Thanks,
> > > Lalitha