Article ID: 307538 - View products that this article applies to.
This article was previously published under Q307538
BUG #: 355405 (SHILOH_BUGS)
In Microsoft SQL Server 7.0 when you start, stop or pause a SQLTrace, SQL Server 7.0 writes an entry that corresponds to one of these events to the Microsoft Windows NT event log. SQL Server 2000 does not implement the same auditing feature.
To resolve this problem, obtain the latest service pack for Microsoft SQL Server 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/290211/EN-US/ )INF: How to Obtain the Latest SQL Server 2000 Service Pack
HotfixNOTE: The following hotfix was created prior to Microsoft SQL Server 2000 Service Pack 2.
The English version of this fix should have the following file attributes or later:
NOTE: Due to file dependencies, the most recent hotfix or feature that contains the preceding files may also contain additional files.
Version File name Platform -------------------------------------- 8.00.443 Sqlservr.exe i386 8.00.443 Sqlevn70.rll i386
Microsoft has confirmed this to be a problem in SQL Server 2000. This problem was first corrected in Microsoft SQL Server 2000 Service Pack 2.
With this fix, SQL Server 2000 now records entries to the Windows NT event log if the following situations occur associated with a SQLTrace:
Each Windows NT event log entry created for these events is an "Information" type entry that is uniquely identified by information in the Description field. The Description field contains an ID, text that describes that ID, the Trace ID, and the LoginName of the user associated with the event.
The possible values for ID and the corresponding text are listed here:
This feature is implemented within SQL Server so that it covers any execution of the sp_trace_setstatus stored procedure, which is used by the SQL Profiler tool to start and stop a SQLTrace.
19030 : SQL Trace started. Trace ID = '1' Login Name = 'MYDOMAIN\myadmin'