Security for server tables on SQL 2000.

[Richard]

I need a user to have access to track all processes logged into our
SQL Server. In other words, I need them to be able to query
master.dbo.sysprocesses. I've already written the query they'll use,
and it works when logged in as sa, but not when logged in as the user
who needs to be able to do this.

I know that on SQL Server 2005, the syntax to grant this permission
would be:

grant view server state to <username>

Unfortunately, I need to do this on an older server running SQL Server
2000, and that syntax doesn't work to grant the permission. Any idea
what I'd need to grant the user to make this work?

Thanks in advance,

--Richard

[Erland Sommarskog]

Richard (bl*********@yahoo.com) writes:

I need a user to have access to track all processes logged into our
SQL Server. In other words, I need them to be able to query
master.dbo.sysprocesses. I've already written the query they'll use,
and it works when logged in as sa, but not when logged in as the user
who needs to be able to do this.

What is the query? What does not "not work" mean?

As far as I recall, the information in sysprocess is public to everyone on
SQL 2000, so this is not likely to be a permission issue, but something
else. Unless someone explicitly has fiddled with the permissions on
sysprocesses. In such case, you should discuss with the DBA before
you fiddle anything more. What does "sp_helprotect sysprocesses" report?


--
Erland Sommarskog, SQL Server MVP, es****@sommarskog.se

Links for SQL Server Books Online:
SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx
SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx
SQL 2000: http://www.microsoft.com/sql/prodinf...ons/books.mspx