How to get rid of a precedence constraint? -
04-27-2006
, 03:22 PM
Hi,
I have created many relatively simple DTS packages from scratch in the past
and they work like a charm. This time, in order to save time (at least that's
what I was hoping), I saved as a package that has a similiar structure with
the one I am currently trying to build. Then I changed all task/steps' names,
queries, servers, workflows, etc to reflect the new structure. Here's what
happened. When I looked at the disconnected edit, old/original workflows (the
ones from the source package) stayed in there although I have deleted all
workflows, i.e. visually there's no workflow left. Or in other words, there
are two precedence steps on each step (assuming there's only one directional
precedence flow) when I add new workflows. This problem has caused my package
stops running after the first task. I have checked individual tasks and they
work fine. Only when I execute the package in its entirety, it keeps failing
on me. Any help on how get rid of those old workflows? Of course, the
ultimate solution would be to build the package from scratch.
Best Regards,
Adrian T |