db fixed role - datareader

Hi,
If I assign a datareader role to a user, can that user execute the stored
procedure? or datareader only means all the select rights, how about
datawriter? Can datawrite execute the stored procedure?
Thanks
Eddatareader = select
datawriter = insert, delete, update
You have to grant execute permission to the user or role.
"Ed" <Ed@.discussions.microsoft.com> wrote in message
news:FF9ED2C9-70E4-4329-8B8A-71D4400907B1@.microsoft.com...
> Hi,
> If I assign a datareader role to a user, can that user execute the stored
> procedure? or datareader only means all the select rights, how about
> datawriter? Can datawrite execute the stored procedure?
> Thanks
> Ed|||No, it only gives SELECT rights. Same for datawriter, it gives (as Richard
says) INSERT, UPDATE, DELETE rights. If you have procedures, they have to
be permissioned separately. It does not extrapolate that you want them to
be able to execute the proc because they have rights to the objects. The
procedure might have a calculation that you don't want the user to have
access to.
----
Louis Davidson - drsql@.hotmail.com
SQL Server MVP
Compass Technology Management - www.compass.net
Pro SQL Server 2000 Database Design -
http://www.apress.com/book/bookDisplay.html?bID=266
Blog - http://spaces.msn.com/members/drsql/
Note: Please reply to the newsgroups only unless you are interested in
consulting services. All other replies may be ignored :)
"Ed" <Ed@.discussions.microsoft.com> wrote in message
news:FF9ED2C9-70E4-4329-8B8A-71D4400907B1@.microsoft.com...
> Hi,
> If I assign a datareader role to a user, can that user execute the stored
> procedure? or datareader only means all the select rights, how about
> datawriter? Can datawrite execute the stored procedure?
> Thanks
> Ed|||In this case what set-up would you recommend for a user that can only read
data, ie datareader but has access to stored procs which may insert data int
o
tables. Is this possible? Thanks.
"Louis Davidson" wrote:

> No, it only gives SELECT rights. Same for datawriter, it gives (as Richar
d
> says) INSERT, UPDATE, DELETE rights. If you have procedures, they have to
> be permissioned separately. It does not extrapolate that you want them to
> be able to execute the proc because they have rights to the objects. The
> procedure might have a calculation that you don't want the user to have
> access to.
> --
> ----
--
> Louis Davidson - drsql@.hotmail.com
> SQL Server MVP
> Compass Technology Management - www.compass.net
> Pro SQL Server 2000 Database Design -
> http://www.apress.com/book/bookDisplay.html?bID=266
> Blog - http://spaces.msn.com/members/drsql/
> Note: Please reply to the newsgroups only unless you are interested in
> consulting services. All other replies may be ignored :)
> "Ed" <Ed@.discussions.microsoft.com> wrote in message
> news:FF9ED2C9-70E4-4329-8B8A-71D4400907B1@.microsoft.com...
>
>