help! report users permission on a SQL 2000 server

From: Wen Ou (WenOu_at_discussions.microsoft.com)
Date: 11/19/04 

Date: Thu, 18 Nov 2004 15:57:01 -0800

hi

There are over 10 databases on my SQL server. I would like to have a report
that shows the user's permission on each database including tables, views and
stored procedures. At this stage, I want to know which user can run or not
stored procedures on each database. Is it possible to find permission using
system stored procedures? I read the online book of SQL server for 3 days.
But I still don't find the system stored procedures.

If this stored produres doesn't exist, I have to write a stored proceduce to
display these user's permission. Could you tell which system tables need to
be used?

Waiting for you
Million thanks in adv

Wen OU

Relevant Pages

  • Re: Unable to view system stored procedures from .NET IDE and unable to debug SQL
    ... But what is the reason for the debug problem I mentioned below? ... try to step into a stored procedure in the Northwind database, ... Run SQL server setup or contact database ... I can't see any system stored procedures in master. ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: Complete Neophyte Question(s)
    ... I have a user named james on a database. ... WITH GRANT is one of the more esotheric features in SQL Server in my ... Or does that depend on the permission? ... CREATE USER erik ...
    (microsoft.public.sqlserver.security)
  • Re: Identical database w/ identical stored procedures?
    ... > creating the maintence nightmare of updating the same stored procedure ... First of all, put your source code, tables, stored procedures and all ... This can be achieved with a help table in the database. ... Erland Sommarskog, SQL Server MVP, esquel@xxxxxxxxxxxxx ...
    (comp.databases.ms-sqlserver)
  • Re: Does nesting stored procedures make sense to increase performance?
    ... Reducing client or middle-tier round trips to the database is a good idea in that it will reduce network traffic. ... In SQL Server 2000, because recompiles of query plans are done on a per-procedure basis, it's helpful some execute one SQL statement per procedure as well. ... If you're going to combine many calls into a single call, you'll need to add robust error handling to the "driver" procedure so as not to call procedures 2,3, and 4 if procedure 1 fails, etc. You'd need to replicate your existing client/middle-tier code's concept of success/failure results quit the batch of procedures on a failure and the return the results/return code that the client/middle-tier sees in the original. ... I've recently became aware of nesting stored procedures in SQL Server. ...
    (microsoft.public.sqlserver.programming)
  • Re: Remote SP debugging from VS 2003: error
    ... "Cannot debug stored procedures because the SQL Server database is not setup ... correctly or user does not have permission to execute master.sp_sdidebug." ... I have configured DCOM on the remote sql server according tothe MSDN ... I have added SQLDebugger account to default permissions in dcom. ...
    (microsoft.public.sqlserver.connect)