"Darren Green" <darren.green@reply-to-newsgroup-sqldts.com> wrote in message
news:zpMxkdY9931AFwGc@sqldts.com...
> In message <10dephpn7oeku7b@corp.supernews.com>, Thomas Scheiderich
> <tfs@deltanet.com> writes
> >I have 50 packages that are going to call one package and I need to set
up a
> >few global variables.
> >
> >Is there an easy way to set up all the packages to have the same Global
> >variables?
> >
> >It is going to take a great deal of time to open each package and add 3
> >variables.
> >
> >Also, what about next month, when we decide we want to track something
else,
> >I will need to do it again.
> >
> >Thanks,
> >
> >Tom.
> >
>
> The best way to do this is to design your packages, in advance, to read
> from a central location, be that a SQL Server table, ini file or
> similar, using the Dynamic Properties Task.
>
> If the packages already exist you could manually alter them to do this
> or write some code to load each package, and the requires tasks, or just
> update the relevant task as a one off.

>
>
> --
> Darren Green (SQL Server MVP)
> DTS - http://www.sqldts.com
>
> PASS - the definitive, global community for SQL Server professionals
> http://www.sqlpass.org
>

>I have 50 packages that are going to call one package and I need to set up a
>few global variables.
>
>Is there an easy way to set up all the packages to have the same Global
>variables?
>
>It is going to take a great deal of time to open each package and add 3
>variables.
>
>Also, what about next month, when we decide we want to track something else,
>I will need to do it again.
>
>Thanks,
>
>Tom.
>