Hello all,
This is for SQL 2000.
A trace is being configured (through a service) with filters to monitor
UPDATE, DELETE or INSERT commands in a particular database. What is weird is
that the system seems to be buffering entries, rather than immediately commit
them to the trace. Only when SQL service is stopped (or the service is
restarted) does the system writes the data to the trace.
Is this something known about SQL 2000?

Regards
Yba

Hi Yba

Yes, this is by design.

The events are buffered until you have 128K, and then they are written to
disk. The alternative, to write each event one row at a time as they occur,
would require so much overhead that tracing could not ever be done on a
production system.

--
HTH
Kalen
----------------------------------------
Kalen Delaney
SQL Server MVP
www.SQLServerInternals.com

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