Re: Detailed User Access Rights
- From: "Dan Guzman" <guzmanda@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 19 Dec 2005 12:47:11 -0600
The Best Practice is to create database roles and grant object permissions
only to roles. You can then control access via role membership. This
greatly simplifies security administration.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"-Ldwater" <Ldwater@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:6F88596D-0A1A-47FB-B56D-9E37EFF3CC94@xxxxxxxxxxxxxxxx
> Right.. i've added those & all is well.
>
> Just as a closing thought.. is there any way I can declare a 'grant'
> command
> to ALL users, current & future?
>
> Its more than likely that once a view / function has been made, it could
> be
> used by other SQL users that will require access, and even though we
> control
> the number of SQL users, it makes more sence to make a function 'global' /
> 'public' rather than having to recode to add a new user each time we
> decide
> to add one.
>
> Thanks!
.
- References:
- Re: Detailed User Access Rights
- From: Dan Guzman
- Re: Detailed User Access Rights
- From: -Ldwater
- Re: Detailed User Access Rights
- From: Dan Guzman
- Re: Detailed User Access Rights
- Prev by Date: Re: Optimization Blows up T-Log
- Next by Date: Re: Getting username
- Previous by thread: Re: Detailed User Access Rights
- Next by thread: Re: SQL 2000 security enforcements (installation)
- Index(es):