Hello, Roberto!
Another solution is
Have a Controller database on a Controller Server.
Create an alias using Client Network Utility to it using a friendly name i.e
MyController
You can then reference this server in your dynamic properties task by using
a query against it.
On each server that you deploy this package to you create an alias with the
same name. This will then enable the package to read from the DB table.
The DB could be hosted on any server this way.
--
Allan Mitchell (Microsoft SQL Server MVP)
MCSE,MCDBA
www.SQLDTS.com I support PASS - the definitive, global community
for SQL Server professionals -
http://www.sqlpass.org [quoted text, click to view] : "Allan Mitchell" <allan@no-spam.sqldts.com> wrote in message
: news:us87pyGRDHA.2036@TK2MSFTNGP12.phx.gbl...
??>> Hello, Roberto!
??>>
??>> I would have a "Common" path for the INI file and always place it in
the
??>> same place every time.
??>>
??>> How to add a Dynamic Properties task to a package and manipulate it
using
??>> VB.
??>>
http://www.sqldts.com/default.aspx?6,102,252,0,1
??>>
??>> --
??>>
??>> Allan Mitchell (Microsoft SQL Server MVP)
??>> MCSE,MCDBA
??>>
www.SQLDTS.com ??>> I support PASS - the definitive, global community
??>> for SQL Server professionals -
http://www.sqlpass.org ??>>
??>> : Exporting in BAS, it seems not bo be a properyt of
dynamictransformation
??>> : task, but related to every item of it
??>>
--- Microsoft Outlook Express 6.00.2800.1158