Groups | Blog | Home
all groups > sql server dts > february 2005 >

sql server dts : Task progress when executing a package via ActiveX


camler
2/18/2005 1:15:02 PM
I am running a package from within another package using ActiveX
script. Everything works fine (global variables are passed and set
between both packages as expected). Can the execution status dialog
show the progress of a child package's tasks (list each task and the
progress)? Any ideas on how to do this or can it be done
programatically? Only one task show in the dialog for the entire child
package and it would be helpful to see each child task as executed.

Thanks,
Cammy
Darren Green
2/18/2005 11:49:15 PM
In message <1108761302.004698.312790@f14g2000cwb.googlegroups.com>,
camler <clerner239@hotmail.com> writes
[quoted text, click to view]

No. This cannot be done, as the dialog shows tasks in the package loaded
directly in the designer. There is no way for the "dialog" to enumerate
tasks in a child package it has no knowledge of.

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

PASS - the definitive, global community for SQL Server professionals
http://www.sqlpass.org
camler
2/22/2005 7:45:38 AM
I may be way off, but do you think you might be able to use the
OnProgress event of the child package to update the dialog window of
the parent package (WinForms or something)? Possibly changing
properties or adding items to the dialog displayed?
Just a thought.

Thanks
Darren Green
2/22/2005 10:12:06 PM
In message <1109087138.761224.167020@f14g2000cwb.googlegroups.com>,
camler <clerner239@hotmail.com> writes
[quoted text, click to view]

The on progress event of a task, not a package, allows you to tell it
how far that task has got, which is what gives you the row counts or %
complete. This is at a task level however, and does not allow you to add
new lines to the dialog. If you wrote your own execute process task you
maybe able to give it some more meaningful progress info, but this is
still just one number for the entire child package.

The dialog is not exposed, and initial population is beyond your
control. The only way to do this would be to write your own execution
control, for the dialog, and your own execute package task that passed
up child events in a format the custom dialog could interpret. Still
almost impossible due to the way packages can change during execution,
so any initial investigation of the package and it's children, which
would be required to populate your custom dialog to start with, but may
not hold true during execution as you could change the child package
that was to be executed for example.

Try and think of DTS as a non-interactive tool, it may help :)

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

PASS - the definitive, global community for SQL Server professionals
http://www.sqlpass.org
AddThis Social Bookmark Button