Select the product you need help with

BUG: Login names that contain leading zero characters are not visible when you use SQL Profiler to audit connections to SQL Server 2000

Article ID: 910741 - View products that this article applies to.

Bug #: 297092 (SQLBUDT)

Acknowledgment: Amichai Shulman of Imperva Inc. contributed to this Microsoft Knowledge Base article.

SYMPTOMS

When you use SQL Profiler in Microsoft SQL Server 2000 to audit connections to SQL Server 2000 by using the Audit Login event class, login names that contain leading zero characters are not visible in the following contexts:

The SQL Profiler graphical user interface
A trace file that is saved by SQL Profiler
A trace table that is saved by SQL Profiler

This problem only applies to SQL Profiler in SQL Server 2000. This problem is fixed in SQL Server 2005 Profiler when you use SQL Server 2005 Profiler to audit connections to SQL Server 2005.

Additionally, you experience the same problem when you use the following methods to audit connections to SQL Server 2000:

You call the sp_who or sp_who2 system stored procedures.
You select the loginname column from the master.dbo.sysprocesses system table.
You view the result set that is returned by the fn_trace_gettable function in SQL Server 2000 Enterprise Manager. For example, this problem occurs when you use the following command:
SELECT * FROM ::fn_trace_gettable('c:\my_trace.trc', default) GO

WORKAROUND

We recommend that you audit connections to SQL Server 2000 by using server-side tracing and by loading the resulting data from a server-side trace file into a database table. To do this, use the fn_trace_gettable function.

For more information about the fn_trace_gettable function, visit the following Microsoft Developer Network (MSDN) Web site:

http://msdn2.microsoft.com/en-us/library/aa258856(SQL.80).aspx

(http://msdn2.microsoft.com/en-us/library/aa258856(SQL.80).aspx)