After a little more searching thru this newsgroup, and then reading (all of)
JP's rant [ :-) ] from a google search, I am left thinking that i) there
*are* issues with the ExecutePkgTask (as we think there are) and ii)we
should stop trying to debug it and just use a different approach.
I *would* be interested in knowing whether other people have encountered
similar issues with nested packages (executepkgtask) and what edition of SQL
they are having them on. We're finding atm, that's it'r primarily
Enterprise Edition with Sp3/3a.
Steve.
"stevo" <intapplications (AT) hotmail (DOT) com> wrote
Quote:
we've now encountered on two client sites, both using SQL2K Enterprise,
that
dtspackages 'fail' with no error logs, windows event logs or DTS logs
generated (DTS log for pkg shows a start but no end entry).
All servers loaded with Sp3. Interestingly, on one site that has Standard
and Ent editions, the standard works with no issues (exactly the same
agent
job and dts packages being executed).
Ideas?
Steve. |