dbTalk Databases Forums  

SSIS: system variables with same name & scope?

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


Discuss SSIS: system variables with same name & scope? in the microsoft.public.sqlserver.dts forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
AT
 
Posts: n/a

Default SSIS: system variables with same name & scope? - 07-28-2006 , 04:36 PM






Hi all -

Running into a problem with SSIS and a google search doesn't yield much
help.

I have a package with multiple tasks and about 10 OnError event
handlers defined (one for each task). I need to go in and change the
System::Propogate variable for some of the event handlers to make sure
that if they fire an Error, it does not propogate up to the package.

The problem is this - I can't match up the system variables to the
actual task event handler in question.

My Variables window shows 10 variables with Name = "Propogate" and
Scope = "OnError" -- even a check of the properties page shows that the
only difference between them is the GUID. There seems to be no way to
match the variable to which task event handler it is scoped to.

No additional columns to add to the Variables window that are relevant,
and even drilling down into the actual event handler, I still see all
of the System variables.

Has anyone encountered this and/or found a workaround?

Thanks,
Jamie


Reply With Quote
  #2  
Old   
Allan Mitchell
 
Posts: n/a

Default Re: SSIS: system variables with same name & scope? - 07-29-2006 , 03:31 AM






Hello jcorning (AT) gmail (DOT) com,


Try adding your own namespace to the variable. In the variables window hit
the button that says "Choose Variable Columns" and choose namespace


Allan

Quote:
Hi all -

Running into a problem with SSIS and a google search doesn't yield
much help.

I have a package with multiple tasks and about 10 OnError event
handlers defined (one for each task). I need to go in and change the
System::Propogate variable for some of the event handlers to make sure
that if they fire an Error, it does not propogate up to the package.

The problem is this - I can't match up the system variables to the
actual task event handler in question.

My Variables window shows 10 variables with Name = "Propogate" and
Scope = "OnError" -- even a check of the properties page shows that
the only difference between them is the GUID. There seems to be no
way to match the variable to which task event handler it is scoped to.

No additional columns to add to the Variables window that are
relevant, and even drilling down into the actual event handler, I
still see all of the System variables.

Has anyone encountered this and/or found a workaround?

Thanks,
Jamie



Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.