On a different thought:

I am in the process of auditing security events using a profiler scripts with the output going directly to a file (for all the reasons previously mentioned in this forum).

The problem that I am running across is that the output to the trace file is being buffered (128K) and if a nasty outage occurs before the buffer is flushed (power supply, blue screen, whatever)then the audited security trace is being lost.

I am new to SQL Server 2000, is there something obvious that I have missed (e.g. bypass buffered writes)?

Any tips would be appreciated.