Re: Security to document databases
- From: "Dan Guzman" <guzmanda@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 19 Sep 2006 21:09:42 -0500
The default public permissions should provide the needed permissions in SQL
2000 to view schema. You shouldn't need to add the user to db_deny* roles
unless you've granted permissions on user objects to public (which is a bad
idea, IMHO). Also, consider using Query Analyzer instead of EM for this
task.
BTW, there are many third party tools that can help automate database
documentation.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Brandon Lilly" <avarice@xxxxxxxxxxxxxxxxx> wrote in message
news:183E8C33-176D-43F8-8FD9-9970FF055C39@xxxxxxxxxxxxxxxx
What are the minimum rights (in SQL 2000) to allow a user to be able to
view
the schema on all database objects on a server, but not allow them to
view/modify any data or execute anything? I tried just adding the user to
all databases and then setting the deny read/write db role, but this
affected
their ability to get a list of database objects in enterprise manager.
Is there a process that someone could point me to that would help for
this.
I am trying to avoid having to set the security on several thousand
database
objects.
Cheers!
Brandon
.
- Prev by Date: Re: **to trace what has happened**
- Next by Date: Re: Locking down SQL Server 2005
- Previous by thread: Re: SQL Server 2005 - Start Up Error 17113
- Next by thread: Re: Locking down SQL Server 2005
- Index(es):
Relevant Pages
|
|
