Re: Logging DTS Jobs

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance



Sammy,

I'm not sure I fully understand your problem, but one thing comes to mind:

When you specify an ErrorLog file, it records the success/failure of each
step in your package. Also, each time you run your package, success/failure
data is APPENDED to the ErrorLog file, not OVERWRITTEN. It's possible that
when you open the ErrorLog file to view, you are only seeing the outcome of
the very first job - not the latest execution, which appears at the end of
the file.

For all of my packages, I specify an external step early on to delete the
ErrorLog file so that only the current job is recorded .. plus it keeps our
SysAdmin happy.

Darren Green eloquently discusses it here:
http://www.sqldts.com/default.aspx?240

- Tom

Thomas Bradshaw
MyWebGrocer.com
Data Integration Services

--
Message posted via SQLMonster.com
http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server-dts/200603/1
.