How should I debug my DTS packages in the production server where there is
no script debugger.



Thanks

JT,

I right click on each object and execute task on each object individually.
If you have code (e.g. ActiveX script), there is a parser which will debug to
a certain level. I've also copied and pasted VB code into other apps (e.g.
Access) VB script editors to get a more complete and informative compile.

When executing each task in a DTS package, it might be worth taking out
broadcast/large scale data tasks and do little jobs first to check your
"code".

Hope the above ideas help.

Cheers,
Leslie

"J-T" wrote:

Thanks for your reply,

What is the parser's name?

Thanks agian


"Leslie" <Leslie (AT) discussions (DOT) microsoft.com> wrote

It's available in the task itself. Open the ActiveX script
task and click on the Parse button

-Sue

On Wed, 27 Jul 2005 14:10:29 -0700, "J-T" <J-T (AT) nospam (DOT) com>
wrote:

Well,I'd like to debug and breakpoint on the first runtime error happens
which parser cannot do that.

Right?

Thanks
"Sue Hoegemeier" <Sue_H (AT) nomail (DOT) please> wrote

No...parsers pretty much just check syntax.

-Sue

On Fri, 29 Jul 2005 11:11:22 -0700, "J-T" <J-T (AT) nospam (DOT) com>
wrote: