I have a problem displaying the correct steplog records of a running dts
package. When I start a job which executes a dts package and try to display
the current log records of this package right after starting the job, I get
log records of the previous 'run'. Waiting a few seconds before getting the
steplog records usually helps, but I want to display them right away (like
running a dts package in enterprise manager).

To get the steplog records of the running package I do the following:

1. get the latest PackageLogRecord, by executing

PackageSQLServer.EnumPackageLogRecords( "package name", true, "", "", "" )

2. find the PackageLogRecord with the latest date in this collection (should
be the log record of the currently running package?)

3. execute PackageSQLServer.EnumStepLogRecords with the LineageFullID of the
PackageLogRecord found in step 2.

It seems to me that there is a delay of some sort in writing the package log
entry in sql server. Do I need to flush something or call refresh on some
object?

Any ideas?

Regards,

Andrew

In message <#8EO1nTIEHA.2836 (AT) TK2MSFTNGP11 (DOT) phx.gbl>, Andrew
<nospamplease@?.?.invalid> writes
If you want info up front then you should use the object model, and
enumerate steps in the package. You can also use events you get progress
info more efficiently than polling via TSQL.

There are some samples and alos KB links in this article for using
events -

Execute a package from Visual Basic (VB)
(http://www.sqldts.com/default.aspx?208,1)
--
Darren Green (SQL Server MVP)
DTS - http://www.sqldts.com

PASS - the definitive, global community for SQL Server professionals
http://www.sqlpass.org