Showing posts with label across. Show all posts
Showing posts with label across. Show all posts

Sunday, February 19, 2012

Cannot Set Connection String For Bulk Insert Source Connection

I came across something strange today. I was wondering I was doing something wrong.

I want to go through a directory and get files and assign the Fully Qualified File Name to a User Variable. I want to use that variable as a connection string within Expression in Bulk Insert Task Source Connection, Data Flow Task and File System Task. It is working fine within Data Flow Task and File System task. It is NOT working for Bulk Insert. Did you come across this or am I doing something wrong?

- Expressions
ConnectionString @.[User::FileName]

Did anyone come across this before?

Thanks

Sutha

Seems to be a problem to me, it does not work within the context of a for each loop, keep getting the error message, connection not valid.

I have written this script and placed it into an activex task before the bulk insert, this seems to fix it.

Dim connmgr As ConnectionManager = Dts.Connections("[your connection name]")
connmgr.ConnectionString = Dts.Variables("User::filename").Value.ToString()
connmgr.AcquireConnection(Nothing)

Hope this helps !

Mark|||

Cheers Mark. It does work fine. I put a script task inside Foreach, just before Bulk Insert to set the connections.

Still thinks its a Bug. Anyone from MS can confirm it. If so do you want me to raise a Bug for this?

Thanks for your help

Sutha

|||

Hello Sutha,

I am trying to achieve the same. Can you help me.

Foreach loop container is reading all the files in the specified folder.

I can also read the variable. But I am having difficulties in assiging this variable file name to Bulk Insert, connection, Source connection.

thanks & regards

radha.

|||I could not reproduce this issue.

1. I could set the value of the "SourceConnection" property to the name of the connection I want to use in my bulk insert task and it works.

2. I can also assign the value of the "ConnectionString" property of the connection to a variable that points to the file and it works.
|||

I am having same issue:

Simple package: Foreach Loop, inside ForEach Loop is a Bulk Insert Task.

I set the variable User::FileName in the variable Mappings of the Foreach Loop. I create a FlatFile connection in connection manager and go into the Expressions of the flat file connection and set the ConnectionString to be @.[User::FileName]. I set the connection in the Bulk Insert to be the Flat file connection I created and I run the package... I get the error: "The specified connection "XYZ Files" is either not valid, or points to an invalid object. To continue, specify a valid connection." Its very reproduceable.

Been fighting with this all day... can someone post step-by-step how to do the workaround where the script sets the connection?

|||Dim connmgr As ConnectionManager = Dts.Connections("Name of Flat File Conn Manager")
connmgr.ConnectionString = Dts.Variables("Var Name of Full path and filename").Value.ToString()
connmgr.AcquireConnection(Nothing)|||See this link for a Dec 27 Blog. http://denster.spaces.live.com/

Cannot Set Connection String For Bulk Insert Source Connection

I came across something strange today. I was wondering I was doing something wrong.

I want to go through a directory and get files and assign the Fully Qualified File Name to a User Variable. I want to use that variable as a connection string within Expression in Bulk Insert Task Source Connection, Data Flow Task and File System Task. It is working fine within Data Flow Task and File System task. It is NOT working for Bulk Insert. Did you come across this or am I doing something wrong?

- Expressions
ConnectionString @.[User::FileName]

Did anyone come across this before?

Thanks

Sutha

Seems to be a problem to me, it does not work within the context of a for each loop, keep getting the error message, connection not valid.

I have written this script and placed it into an activex task before the bulk insert, this seems to fix it.

Dim connmgr As ConnectionManager = Dts.Connections("[your connection name]")
connmgr.ConnectionString = Dts.Variables("User::filename").Value.ToString()
connmgr.AcquireConnection(Nothing)

Hope this helps !

Mark|||

Cheers Mark. It does work fine. I put a script task inside Foreach, just before Bulk Insert to set the connections.

Still thinks its a Bug. Anyone from MS can confirm it. If so do you want me to raise a Bug for this?

Thanks for your help

Sutha

|||

Hello Sutha,

I am trying to achieve the same. Can you help me.

Foreach loop container is reading all the files in the specified folder.

I can also read the variable. But I am having difficulties in assiging this variable file name to Bulk Insert, connection, Source connection.

thanks & regards

radha.

|||I could not reproduce this issue.

1. I could set the value of the "SourceConnection" property to the name of the connection I want to use in my bulk insert task and it works.

2. I can also assign the value of the "ConnectionString" property of the connection to a variable that points to the file and it works.
|||

I am having same issue:

Simple package: Foreach Loop, inside ForEach Loop is a Bulk Insert Task.

I set the variable User::FileName in the variable Mappings of the Foreach Loop. I create a FlatFile connection in connection manager and go into the Expressions of the flat file connection and set the ConnectionString to be @.[User::FileName]. I set the connection in the Bulk Insert to be the Flat file connection I created and I run the package... I get the error: "The specified connection "XYZ Files" is either not valid, or points to an invalid object. To continue, specify a valid connection." Its very reproduceable.

Been fighting with this all day... can someone post step-by-step how to do the workaround where the script sets the connection?

|||Dim connmgr As ConnectionManager = Dts.Connections("Name of Flat File Conn Manager")
connmgr.ConnectionString = Dts.Variables("Var Name of Full path and filename").Value.ToString()
connmgr.AcquireConnection(Nothing)|||See this link for a Dec 27 Blog. http://denster.spaces.live.com/

Cannot Set Connection String For Bulk Insert Source Connection

I came across something strange today. I was wondering I was doing something wrong.

I want to go through a directory and get files and assign the Fully Qualified File Name to a User Variable. I want to use that variable as a connection string within Expression in Bulk Insert Task Source Connection, Data Flow Task and File System Task. It is working fine within Data Flow Task and File System task. It is NOT working for Bulk Insert. Did you come across this or am I doing something wrong?

- Expressions
ConnectionString @.[User::FileName]

Did anyone come across this before?

Thanks

Sutha

Seems to be a problem to me, it does not work within the context of a for each loop, keep getting the error message, connection not valid.

I have written this script and placed it into an activex task before the bulk insert, this seems to fix it.

Dim connmgr As ConnectionManager = Dts.Connections("[your connection name]")
connmgr.ConnectionString = Dts.Variables("User::filename").Value.ToString()
connmgr.AcquireConnection(Nothing)

Hope this helps !

Mark|||

Cheers Mark. It does work fine. I put a script task inside Foreach, just before Bulk Insert to set the connections.

Still thinks its a Bug. Anyone from MS can confirm it. If so do you want me to raise a Bug for this?

Thanks for your help

Sutha

|||

Hello Sutha,

I am trying to achieve the same. Can you help me.

Foreach loop container is reading all the files in the specified folder.

I can also read the variable. But I am having difficulties in assiging this variable file name to Bulk Insert, connection, Source connection.

thanks & regards

radha.

|||I could not reproduce

this issue.

1. I could set the value of the "SourceConnection" property to

the name of the connection I want to use in my bulk insert task and it

works.

2. I can also assign the value of the "ConnectionString" property of the connection to a variable that points to the file and it works.

|||

I am having same issue:

Simple package: Foreach Loop, inside ForEach Loop is a Bulk Insert Task.

I set the variable User::FileName in the variable Mappings of the Foreach Loop. I create a FlatFile connection in connection manager and go into the Expressions of the flat file connection and set the ConnectionString to be @.[User::FileName]. I set the connection in the Bulk Insert to be the Flat file connection I created and I run the package... I get the error: "The specified connection "XYZ Files" is either not valid, or points to an invalid object. To continue, specify a valid connection." Its very reproduceable.

Been fighting with this all day... can someone post step-by-step how to do the workaround where the script sets the connection?

|||Dim connmgr As ConnectionManager = Dts.Connections("Name of Flat File Conn Manager")
connmgr.ConnectionString = Dts.Variables("Var Name of Full path and filename").Value.ToString()
connmgr.AcquireConnection(Nothing)|||See this link for a Dec 27 Blog. http://denster.spaces.live.com/

Cannot Set Connection String For Bulk Insert Source Connection

I came across something strange today. I was wondering I was doing something wrong.

I want to go through a directory and get files and assign the Fully Qualified File Name to a User Variable. I want to use that variable as a connection string within Expression in Bulk Insert Task Source Connection, Data Flow Task and File System Task. It is working fine within Data Flow Task and File System task. It is NOT working for Bulk Insert. Did you come across this or am I doing something wrong?

- Expressions
ConnectionString @.[User::FileName]

Did anyone come across this before?

Thanks

Sutha

Seems to be a problem to me, it does not work within the context of a for each loop, keep getting the error message, connection not valid.

I have written this script and placed it into an activex task before the bulk insert, this seems to fix it.

Dim connmgr As ConnectionManager = Dts.Connections("[your connection name]")
connmgr.ConnectionString = Dts.Variables("User::filename").Value.ToString()
connmgr.AcquireConnection(Nothing)

Hope this helps !

Mark|||

Cheers Mark. It does work fine. I put a script task inside Foreach, just before Bulk Insert to set the connections.

Still thinks its a Bug. Anyone from MS can confirm it. If so do you want me to raise a Bug for this?

Thanks for your help

Sutha

|||

Hello Sutha,

I am trying to achieve the same. Can you help me.

Foreach loop container is reading all the files in the specified folder.

I can also read the variable. But I am having difficulties in assiging this variable file name to Bulk Insert, connection, Source connection.

thanks & regards

radha.

|||I could not reproduce

this issue.

1. I could set the value of the "SourceConnection" property to

the name of the connection I want to use in my bulk insert task and it

works.

2. I can also assign the value of the "ConnectionString" property of the connection to a variable that points to the file and it works.

|||

I am having same issue:

Simple package: Foreach Loop, inside ForEach Loop is a Bulk Insert Task.

I set the variable User::FileName in the variable Mappings of the Foreach Loop. I create a FlatFile connection in connection manager and go into the Expressions of the flat file connection and set the ConnectionString to be @.[User::FileName]. I set the connection in the Bulk Insert to be the Flat file connection I created and I run the package... I get the error: "The specified connection "XYZ Files" is either not valid, or points to an invalid object. To continue, specify a valid connection." Its very reproduceable.

Been fighting with this all day... can someone post step-by-step how to do the workaround where the script sets the connection?

|||Dim connmgr As ConnectionManager = Dts.Connections("Name of Flat File Conn Manager")
connmgr.ConnectionString = Dts.Variables("Var Name of Full path and filename").Value.ToString()
connmgr.AcquireConnection(Nothing)|||See this link for a Dec 27 Blog. http://denster.spaces.live.com/

Cannot Set Connection String For Bulk Insert Source Connection

I came across something strange today. I was wondering I was doing something wrong.

I want to go through a directory and get files and assign the Fully Qualified File Name to a User Variable. I want to use that variable as a connection string within Expression in Bulk Insert Task Source Connection, Data Flow Task and File System Task. It is working fine within Data Flow Task and File System task. It is NOT working for Bulk Insert. Did you come across this or am I doing something wrong?

- Expressions
ConnectionString @.[User::FileName]

Did anyone come across this before?

Thanks

Sutha

Seems to be a problem to me, it does not work within the context of a for each loop, keep getting the error message, connection not valid.

I have written this script and placed it into an activex task before the bulk insert, this seems to fix it.

Dim connmgr As ConnectionManager = Dts.Connections("[your connection name]")
connmgr.ConnectionString = Dts.Variables("User::filename").Value.ToString()
connmgr.AcquireConnection(Nothing)

Hope this helps !

Mark|||

Cheers Mark. It does work fine. I put a script task inside Foreach, just before Bulk Insert to set the connections.

Still thinks its a Bug. Anyone from MS can confirm it. If so do you want me to raise a Bug for this?

Thanks for your help

Sutha

|||

Hello Sutha,

I am trying to achieve the same. Can you help me.

Foreach loop container is reading all the files in the specified folder.

I can also read the variable. But I am having difficulties in assiging this variable file name to Bulk Insert, connection, Source connection.

thanks & regards

radha.

|||I could not reproduce this issue.

1. I could set the value of the "SourceConnection" property to the name of the connection I want to use in my bulk insert task and it works.

2. I can also assign the value of the "ConnectionString" property of the connection to a variable that points to the file and it works.
|||

I am having same issue:

Simple package: Foreach Loop, inside ForEach Loop is a Bulk Insert Task.

I set the variable User::FileName in the variable Mappings of the Foreach Loop. I create a FlatFile connection in connection manager and go into the Expressions of the flat file connection and set the ConnectionString to be @.[User::FileName]. I set the connection in the Bulk Insert to be the Flat file connection I created and I run the package... I get the error: "The specified connection "XYZ Files" is either not valid, or points to an invalid object. To continue, specify a valid connection." Its very reproduceable.

Been fighting with this all day... can someone post step-by-step how to do the workaround where the script sets the connection?

|||Dim connmgr As ConnectionManager = Dts.Connections("Name of Flat File Conn Manager")
connmgr.ConnectionString = Dts.Variables("Var Name of Full path and filename").Value.ToString()
connmgr.AcquireConnection(Nothing)|||See this link for a Dec 27 Blog. http://denster.spaces.live.com/

Thursday, February 16, 2012

Cannot seem to connect to named instance

We are trying to connect to a SQL Server across the WAN. We can manage to
ping the server and know that SQL Server is online on the other end as on
the own internal network, we can connect to it.. but across the WAN, we
cannot. We are thinking its a port issue that needs to be opened. So the
question is do I only need to open the port that named instance is listening
on or do I have to open up some other ports too. I believe for named
instances, there is something to do with UDP port too. Let me know if i have
to open up UDP port 1434 too to get this to work.
> Let me know if i have to open up UDP port 1434 too to get this to work.
Yes, you'll need to open up UDP port 1434 for named instance port
enumeration as well as the named instance port TCP port. Alternatively, you
can create an alias for the named instance on the client machine and specify
the named instance port number. You won't need to open UDP 1434 in that
case.
Hope this helps.
Dan Guzman
SQL Server MVP
"Hassan" <hassan@.hotmail.com> wrote in message
news:ueLdNA41HHA.1188@.TK2MSFTNGP04.phx.gbl...
> We are trying to connect to a SQL Server across the WAN. We can manage to
> ping the server and know that SQL Server is online on the other end as on
> the own internal network, we can connect to it.. but across the WAN, we
> cannot. We are thinking its a port issue that needs to be opened. So the
> question is do I only need to open the port that named instance is
> listening on or do I have to open up some other ports too. I believe for
> named instances, there is something to do with UDP port too. Let me know
> if i have to open up UDP port 1434 too to get this to work.
>
>

Cannot seem to connect to named instance

We are trying to connect to a SQL Server across the WAN. We can manage to
ping the server and know that SQL Server is online on the other end as on
the own internal network, we can connect to it.. but across the WAN, we
cannot. We are thinking its a port issue that needs to be opened. So the
question is do I only need to open the port that named instance is listening
on or do I have to open up some other ports too. I believe for named
instances, there is something to do with UDP port too. Let me know if i have
to open up UDP port 1434 too to get this to work.> Let me know if i have to open up UDP port 1434 too to get this to work.
Yes, you'll need to open up UDP port 1434 for named instance port
enumeration as well as the named instance port TCP port. Alternatively, you
can create an alias for the named instance on the client machine and specify
the named instance port number. You won't need to open UDP 1434 in that
case.
Hope this helps.
Dan Guzman
SQL Server MVP
"Hassan" <hassan@.hotmail.com> wrote in message
news:ueLdNA41HHA.1188@.TK2MSFTNGP04.phx.gbl...
> We are trying to connect to a SQL Server across the WAN. We can manage to
> ping the server and know that SQL Server is online on the other end as on
> the own internal network, we can connect to it.. but across the WAN, we
> cannot. We are thinking its a port issue that needs to be opened. So the
> question is do I only need to open the port that named instance is
> listening on or do I have to open up some other ports too. I believe for
> named instances, there is something to do with UDP port too. Let me know
> if i have to open up UDP port 1434 too to get this to work.
>
>|||On the below thread and similar issue, how can I hard code SQL Instance to
use the same port number?
Any suggestions?
"Dan Guzman" wrote:
> > Let me know if i have to open up UDP port 1434 too to get this to work.
> Yes, you'll need to open up UDP port 1434 for named instance port
> enumeration as well as the named instance port TCP port. Alternatively, you
> can create an alias for the named instance on the client machine and specify
> the named instance port number. You won't need to open UDP 1434 in that
> case.
>
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "Hassan" <hassan@.hotmail.com> wrote in message
> news:ueLdNA41HHA.1188@.TK2MSFTNGP04.phx.gbl...
> > We are trying to connect to a SQL Server across the WAN. We can manage to
> > ping the server and know that SQL Server is online on the other end as on
> > the own internal network, we can connect to it.. but across the WAN, we
> > cannot. We are thinking its a port issue that needs to be opened. So the
> > question is do I only need to open the port that named instance is
> > listening on or do I have to open up some other ports too. I believe for
> > named instances, there is something to do with UDP port too. Let me know
> > if i have to open up UDP port 1434 too to get this to work.
> >
> >
> >
>|||> On the below thread and similar issue, how can I hard code SQL Instance to
> use the same port number?
You can specify the server port number using the SQL Server Network Utility
(SQL 2000) or the SQL Server Configuration Manager (SQL 2005). See
http://support.microsoft.com/kb/823938.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Mehul" <Mehul@.discussions.microsoft.com> wrote in message
news:A80C2723-4EB2-4BD0-92D1-619DF2FCF527@.microsoft.com...
> On the below thread and similar issue, how can I hard code SQL Instance to
> use the same port number?
> Any suggestions?
> "Dan Guzman" wrote:
>> > Let me know if i have to open up UDP port 1434 too to get this to work.
>> Yes, you'll need to open up UDP port 1434 for named instance port
>> enumeration as well as the named instance port TCP port. Alternatively,
>> you
>> can create an alias for the named instance on the client machine and
>> specify
>> the named instance port number. You won't need to open UDP 1434 in that
>> case.
>>
>> --
>> Hope this helps.
>> Dan Guzman
>> SQL Server MVP
>> "Hassan" <hassan@.hotmail.com> wrote in message
>> news:ueLdNA41HHA.1188@.TK2MSFTNGP04.phx.gbl...
>> > We are trying to connect to a SQL Server across the WAN. We can manage
>> > to
>> > ping the server and know that SQL Server is online on the other end as
>> > on
>> > the own internal network, we can connect to it.. but across the WAN, we
>> > cannot. We are thinking its a port issue that needs to be opened. So
>> > the
>> > question is do I only need to open the port that named instance is
>> > listening on or do I have to open up some other ports too. I believe
>> > for
>> > named instances, there is something to do with UDP port too. Let me
>> > know
>> > if i have to open up UDP port 1434 too to get this to work.
>> >
>> >
>> >
>>

Cannot seem to connect to named instance

We are trying to connect to a SQL Server across the WAN. We can manage to
ping the server and know that SQL Server is online on the other end as on
the own internal network, we can connect to it.. but across the WAN, we
cannot. We are thinking its a port issue that needs to be opened. So the
question is do I only need to open the port that named instance is listening
on or do I have to open up some other ports too. I believe for named
instances, there is something to do with UDP port too. Let me know if i have
to open up UDP port 1434 too to get this to work.> Let me know if i have to open up UDP port 1434 too to get this to work.
Yes, you'll need to open up UDP port 1434 for named instance port
enumeration as well as the named instance port TCP port. Alternatively, you
can create an alias for the named instance on the client machine and specify
the named instance port number. You won't need to open UDP 1434 in that
case.
Hope this helps.
Dan Guzman
SQL Server MVP
"Hassan" <hassan@.hotmail.com> wrote in message
news:ueLdNA41HHA.1188@.TK2MSFTNGP04.phx.gbl...
> We are trying to connect to a SQL Server across the WAN. We can manage to
> ping the server and know that SQL Server is online on the other end as on
> the own internal network, we can connect to it.. but across the WAN, we
> cannot. We are thinking its a port issue that needs to be opened. So the
> question is do I only need to open the port that named instance is
> listening on or do I have to open up some other ports too. I believe for
> named instances, there is something to do with UDP port too. Let me know
> if i have to open up UDP port 1434 too to get this to work.
>
>

Friday, February 10, 2012

Cannot resolve a package path

I have a parent package - Main.dtsx that calls a number of child packages. I also use configuration packages as I must deploy the application across multiple environments.

Main.dtsx contains a single Ccnfiguration file - Child_Packages.dtsConfig. This contains the connection strings for all the child packages.

Each child package contains a single configuration file - Main.dtsConfig that contains a superset of OLE DB connections. That is no single child package uses all of the connections contained in main.dtsConfig.

Each child package will execute independently without error. However, when called from Main.dtsx, I get the following errors:

Error: 2007-08-15 15:44:22.93
Code: 0xC001000E
Source: UserSecurity
Description: The connection "CRM" is not found. This error is thrown by Connections collection when the specific connection element is not found.
End Error
Warning: 2007-08-15 15:44:22.93
Code: 0x8001F02F
Source: UserSecurity
Description: Cannot resolve a package path to an object in the package ".Connections[CRM].Properties[ConnectionString]". Verify that the package path is valid.
End Warning
Warning: 2007-08-15 15:44:22.94
Code: 0x80012017
Source: UserSecurity
Description: The package path referenced an object that cannot be found: "\Package.Connections[CRM].Properties[ConnectionString]". This occurs when an attempt is made to resolve a package path to an object that cannot be found.
End Warning


I have seen discussions that suggest that these errors occur where the connection in the config file is not found in the child package. Is there any way of suppressing this ?

Are there any simpler methods that allow me to change connections in each environment?

I suspect I will end up having to tailor config files for each child package, but I live in hope.

Michael M.

Duh! The main cause of this error is the fact that the child packages do not contain all of the connections that are in Main.dtsConfig.

But it is a pain to have to add connections that you don't use to each package.

And it is pain that you can't use the Deployment utility because it crashes attempting to copy the same config files over.

|||

You can use individual configuration files if you want; that way each package uses only the config files that really requires. BTW, I think, a package does not fail because the configuration file has an entry that is not used by that package; rather you see a warning.

|||

Regarding: BTW, I think, a package does not fail...

What caused this error?

Code Snippet

Error: 2007-08-15 15:44:22.93
Code: 0xC001000E
Source: UserSecurity
Description: The connection "CRM" is not found. This error is thrown by Connections collection when the specific connection element is not found.
End Error

As to writing individual config files, this is creates unneccessary work, IMHO. Other ETL packages can use a single config file.

The best solution would be to build a tool that updates the .dtsx files in each environment and then we don't need config files at all.

Cannot resolve a package path

I have a parent package - Main.dtsx that calls a number of child packages. I also use configuration packages as I must deploy the application across multiple environments.

Main.dtsx contains a single Ccnfiguration file - Child_Packages.dtsConfig. This contains the connection strings for all the child packages.

Each child package contains a single configuration file - Main.dtsConfig that contains a superset of OLE DB connections. That is no single child package uses all of the connections contained in main.dtsConfig.

Each child package will execute independently without error. However, when called from Main.dtsx, I get the following errors:

Error: 2007-08-15 15:44:22.93
Code: 0xC001000E
Source: UserSecurity
Description: The connection "CRM" is not found. This error is thrown by Connections collection when the specific connection element is not found.
End Error
Warning: 2007-08-15 15:44:22.93
Code: 0x8001F02F
Source: UserSecurity
Description: Cannot resolve a package path to an object in the package ".Connections[CRM].Properties[ConnectionString]". Verify that the package path is valid.
End Warning
Warning: 2007-08-15 15:44:22.94
Code: 0x80012017
Source: UserSecurity
Description: The package path referenced an object that cannot be found: "\Package.Connections[CRM].Properties[ConnectionString]". This occurs when an attempt is made to resolve a package path to an object that cannot be found.
End Warning


I have seen discussions that suggest that these errors occur where the connection in the config file is not found in the child package. Is there any way of suppressing this ?

Are there any simpler methods that allow me to change connections in each environment?

I suspect I will end up having to tailor config files for each child package, but I live in hope.

Michael M.

Duh! The main cause of this error is the fact that the child packages do not contain all of the connections that are in Main.dtsConfig.

But it is a pain to have to add connections that you don't use to each package.

And it is pain that you can't use the Deployment utility because it crashes attempting to copy the same config files over.

|||

You can use individual configuration files if you want; that way each package uses only the config files that really requires. BTW, I think, a package does not fail because the configuration file has an entry that is not used by that package; rather you see a warning.

|||

Regarding: BTW, I think, a package does not fail...

What caused this error?

Code Snippet

Error: 2007-08-15 15:44:22.93
Code: 0xC001000E
Source: UserSecurity
Description: The connection "CRM" is not found. This error is thrown by Connections collection when the specific connection element is not found.
End Error

As to writing individual config files, this is creates unneccessary work, IMHO. Other ETL packages can use a single config file.

The best solution would be to build a tool that updates the .dtsx files in each environment and then we don't need config files at all.