Re: Global Variables In DTS Package

#1

In article <00ea01c346f4$fc23e040$a101280a (AT) phx (DOT) gbl>, Ken
<kackimenko (AT) ama (DOT) ab.ca> writes

Quote:

I have some Global Variables in a DTS Package that are
updated inside the package. When I run the package
manually, the variables update the way I expect them to.
When I run the same DTS package via a scheduled job, the
job runs successfully, however, the variables do not
appear to have been updated. Anyone no why? I need to
save dates in these global variables so that when the job
runs month to month, these dates can be changed and made
available the following month when the job runs again.

Thanks for your help.

When you run the package the variable may change during run-time but
unless you then save the package again they will not be persisted. When
you run it manually after execution the values from run-time are still
there, but if you close the package without saving they will not be
persisted either.

The thing to do is to use a table to keep track of these values. You can
use the Exec SQL Task to read and write the values using the parameter
options of the task.

--
Darren Green (SQL Server MVP)
DTS - http://www.sqldts.com

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

Re: Global Variables In DTS Package

microsoft.public.sqlserver.dts microsoft.public.sqlserver.dts

Re: Global Variables In DTS Package - 07-10-2003 , 03:04 PM