Re: Removing Permissions from the public role
- From: Jay B <jayB@xxxxxxxxxxx>
- Date: Mon, 27 Nov 2006 16:27:35 -0500
did you think about putting those 8 tables in a different schema, and then just granting rights to that schema, revoking the rights for that group from public.
BrianK wrote:
I have to allow another application a connection to my database and.
only grant them select rights to about 8 tables out of a possible 150
tables in this database. I created a new login and added a new role for
that user and ran some grant scripts to allow them to select from the 8
tables they need to select data from. I see that there is a public role
added by default for all new logins that are created. It seems as if
the public security role is still allowing the new login access to all
of the tables in the database. Rather then have 150 lines of T-SQL to
revoke the select permission from the public role is there an easier
way to do this (NOT THROUGH EM ONLY T-SQL). Below are the scripts that
i used to create the new login:
sp_addlogin 'briank','briank','Northwind'
sp_addrole 'lookup'
sp_grantdbaccess 'briank','briank'
sp_addrolemember 'lookup',briank
GRANT SELECT ON PDF TO briank
GRANT SELECT ON SOCIAL TO briank
Any insight would be appreciated
- Follow-Ups:
- Re: Removing Permissions from the public role
- From: Arnie Rowland
- Re: Removing Permissions from the public role
- References:
- Removing Permissions from the public role
- From: BrianK
- Removing Permissions from the public role
- Prev by Date: Removing Permissions from the public role
- Next by Date: Re: Installing SQL Server 2005 on Vista RTM
- Previous by thread: Removing Permissions from the public role
- Next by thread: Re: Removing Permissions from the public role
- Index(es):
Relevant Pages
|