Re: sql2k5 security
- From: <param@xxxxxxxxxxxxxxxx>
- Date: Fri, 23 Jun 2006 23:01:08 -0500
I guess I am missing something. In SQL 2000 I was able to give a user only
Execute permissions on a stored proc and the stored proc was able to perform
select/insert/update/delete operations fine. Now this doesnt seem to work in
SQL2005? I have to explicity give the user select/insert/update/delete
permissions on the tables?
"Wei Lu [MSFT]" <weilu@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:uSb9cOelGHA.4164@xxxxxxxxxxxxxxxxxxxxxxxx
Hi param,
Have you got any further ideas on this issue or does my last reply also
help some? If there is still anything we can help, please feel free to
post
here.
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================
This posting is provided "AS IS" with no warranties, and confers no
rights.
.
- Follow-Ups:
- Re: sql2k5 security
- From: Wei Lu [MSFT]
- Re: sql2k5 security
- From: David Browne
- Re: sql2k5 security
- References:
- sql2k5 security
- From: param
- Re: sql2k5 security
- From: David Browne
- Re: sql2k5 security
- From: param
- Re: sql2k5 security
- From: Wei Lu
- Re: sql2k5 security
- From: param
- Re: sql2k5 security
- From: Wei Lu
- Re: sql2k5 security
- From: Wei Lu [MSFT]
- sql2k5 security
- Prev by Date: Re: setup an asymmetric key
- Next by Date: Re: SQL2005 security
- Previous by thread: Re: sql2k5 security
- Next by thread: Re: sql2k5 security
- Index(es):