all groups > sql server dts > may 2006 >
You're in the

sql server dts

group:

Indirect SQL Server Package Configuration


Indirect SQL Server Package Configuration Dennis Forbes
5/26/2006 10:50:01 AM
sql server dts: What data is SSIS expecting to be stored in an environment variable when you
opt for indirect SQL Server package configuration? The documentation on this
RE: Indirect SQL Server Package Configuration Dennis Forbes
5/30/2006 7:22:02 AM
If anyone from Microsoft, or an eager-to-be MVPs, comes by this post, I would
really appreciate an answer. This isn't actually documented in the SQL Server
documentation (including the most up-to-date documentation), and without
knowing WHAT to store in the environment variable (presumably a link to the
database server and table...it wouldn't be silly enough to store a link to
another connection in the package), it is of negligible benefit.

[quoted text, click to view]
RE: Indirect SQL Server Package Configuration Allan Mitchell
5/30/2006 11:28:11 AM
Hello Dennis,


The thing that is stored in the Environment variable is up to you but it
needs to look like the configuration string property in the configuration
setup.

Examples


If I was using a direct XML file the property would look like this

C:\MyConfigFile.dtsConfig

The indirect XML Configuration would place "C:\MyConfigFile.dtsConfig" in
an Environment variable


If I was using a direct SQL Server Configuration the property may look like
this

"(local).tempDB";"[dbo].[SSIS Configurations]";"ConfigTable";


The indirect version of this configuration would place "(local).tempDB";"[dbo].[SSIS
Configurations]";"ConfigTable"; in the environment variable.


Does that help?


Allan Mitchell
www.SQLDTS.com
www.SQLIS.com
www.Konesans.com

[quoted text, click to view]

RE: Indirect SQL Server Package Configuration Dennis Forbes
5/31/2006 9:32:01 AM
Hi there Allan.

Indeed, what you mentioned is what I originally tried, as it seems logical.
The problem with it, however, is that the server/database mentioned is only
an alias to a pre-existing connection in the connection manager. So I already
have to have a "Configuration" connection to reference in the environment
variable, and of course I can't make that connection configurable because it
needs it to get the configuration in the first place. Absolutely insane, and
inane, at the same time.

If this is true, and I can't provide an arbitrary connection to a runtime
chosen destination, then it viciously snatches defeat from the hand of
defeat, and makes indirect SQL Server configuration laughably useless.

[quoted text, click to view]
AddThis Social Bookmark Button