Set Global Variables in DTS package fail

Question

Set Global Variables in DTS package fail

mhweiss

SSCarpal Tunnel

Points: 4284
More actions
March 25, 2003 at 3:30 pm

#105637

I have a DTS package that has been running without fail for about a year. Approximately a week ago, two of the execute sql tasks that set global variables stopped setting the value of the variables. These tasks get the starting id number in a table before insert and the ending id number after the insert has completed. This information is then used in the filter for an incremental processing of an analysis services cube. I can't figure out why these two global variables are no longer being set...any ideas on where to start looking or possible remedies?
Thank you,
Michael

Michael Weiss

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply

philcart SSC-Forever Points: 47796 More actions · Answer 1

Check the Global Variable definition. A couple of times I've had variables with the datatype set to dispatch with the value set to <not displayable>. The only way I was able to successfully assign a value to the variable was to delete it and redefine it.

Hope this helps

Phill Carter

--------------------

Colt 45 - the original point and click interface

--------------------
Colt 45 - the original point and click interface

mhweiss SSCarpal Tunnel Points: 4284 More actions · Answer 2

Thank you, Phill. I looked at the variables' properties and everything looked fine...in fact I couldn't find anywhere that the datatype could be 'dispatch' so either I am confused or I am missing something. Now you have me intrigued...what is 'dispatch'? I can execute each of these two steps manually via dts designer and the variable values are set appropriately. Does that help narrow the problem down?

Thanks again,

Michael

Michael Weiss

philcart SSC-Forever Points: 47796 More actions · Answer 3

I couldn't find anything about 'dispatch' either, that was why I resorted to deleting the variable and recreating it.

Generally it appeared when I was assigning a value to a variable from the ExecuteSQL task and the SQL statement executed didn't return any results.