on my company's developement sql server, I created a DTS package with a
global variable. Then from an ASP page I pass a value to a stored procedure
which sets a global variable in the DTS package and then the stored procedure
executes the DTS package. It all works on the development server! The
problem I am having is that I have moved the DTS package up to our Test sql
server and tried running it again but for some reason it is not working.
Either the gobal variable is not getting set or I am not able to read it?
When I do try to read the global variable, I just get the default value that
I specify when I created it - not the value that I am passing to the stored
procedure. All of the code is exactly the same - I have changed nothing!! I
am working with our DBA on this but haven't been able to figure out why this
is not working. Does anyone have any ideas?? Is there some setting in SQL
Server that needs to be set??

thanks
Kurt

You could add some logging to the package to write out the variables at
run-time, so this will confirm if the variable is set.

Global variable diagnostic script
(http://www.sqldts.com/default.aspx?303)

Some things to watch out for-

Global variable names are case sensitive.
Check that you are executing the correct package, use the name, or verify
the package/version GUIDs are the same as often they change when moving
packages between servers.



--
Darren Green
http://www.sqldts.com
http://www.sqlis.com


"kurtn" <kurtn (AT) discussions (DOT) microsoft.com> wrote