We have some very large DTS packages that are run nightly.

We they fail it is often difficult to diagnose because the error
details in Job History is truncated.  Is this information written to a
log anywhere, or is there a setting to increase the amount of
information that is stored?

Or... am I stuck with logging each step.

Thanks for the help,

DG

Any ideas?  I havent been able to find any info on this.  I know others
must be having the same problems.

Hi

I believe the job step details are taken from the message column of the
sysjobhistory table which is limited to 1024 characters.

John

Show quoteHide quote

Any ideas?  I havent been able to find any info on this.  I know others
must be having the same problems.

Any ideas?  I havent been able to find any info on this.  I know others
must be having the same problems.

JDBC client - CURSOR as OUT parameter -supported ?
Creating a trigger using a cursor
Just Venting
SQL Join and Where to Put the 'ON'
Error message in a job, SQLSTATE 42S02 (Error 208)