Is this not a simple case of detecting the custom task ID and if it is not
one you recognise then it is a "user" defined task. You just build up a list
of the MS tasks for comparison. There are other MS tasks out there that
don't ship with SQL Server, so you may want to tighten your definition of
"user" defined, and say not part of the core product. This is probably what
most people would care about as then you have implications for package
deployment to ensure all tasks used are available on the target machine.
--
Darren Green
http://www.sqldts.com
"Venkatesh Iyengar" <venkateshi (AT) covelix (DOT) com> wrote
Quote:
I am parsing all the available packages on SQL Server 2K while parsing
individual package i scan all the tasks in the
package and using the customtaskid property of the task object i determine
wether it is a DTSDDQTask or Parallel Data Pump task.
But i dont know how to detect wether a task is a DTS task implemented by
others.Because the customtaskid property gives me the classid which
can be different for different customtasks depending on progid.
Any help on this will be very helpful.
Regards
Venkatesh |