BUG: BOL Incorrectly States That Users Do Not Need to Be Sysadmin to Use Profiler or SQL Profiler SPs (310175)



The information in this article applies to:

  • Microsoft SQL Server 2000 (all editions)

This article was previously published under Q310175
BUG #: 352071 (SHILOH_BUGS)

SYMPTOMS

In the "Monitoring with SQL Profiler" topic in SQL Server Books Online, the passage subsection "Starting SQL Profiler" is incorrect. The following excerpt is from "Starting SQL Profiler":

With Windows Authentication mode, the user account that runs SQL Profiler must be granted permission to connect to an instance of SQL Server. The login account also must be granted permissions to execute SQL Profiler stored procedures.

If a user is not a member of the sysadmin server role and attempts to use SQL Profiler, the following error message occurs:
In order to run a trace against SQL Server you have to be a member of sysadmin fixed server role.
The user must be a member of the sysadmin server role to run the SQL Profiler procedures. Only members of the sysadmin server role can execute these stored procedures:
  • sp_trace_create
  • sp_trace_generateevent
  • sp_trace_setevent
  • sp_trace_setfilter
  • sp_trace_setstatus
Even if you grant execute permission for the preceding list of stored procedures to a user who is not a member of the sysadmin server role, the execute fails with a permission denied error message as follows:
Server: Msg 262, Level 14, State 6, Procedure %ls, Line 1 %ls permission denied in database '%.*ls'.

STATUS

Microsoft has confirmed this to be a problem in SQL Server 2000 Books Online.

MORE INFORMATION

In SQL Server 2000, users who are not members of the sysadmin server role cannot use SQL Profiler and the SQL Profiler stored procedures.

Modification Type:MajorLast Reviewed:10/3/2003
Keywords:kbbug kbpending KB310175