Re: sql2k5 security
- From: "David Browne" <davidbaxterbrowne no potted meat@xxxxxxxxxxx>
- Date: Sun, 25 Jun 2006 08:38:38 -0500
<param@xxxxxxxxxxxxxxxx> wrote in message news:%23tsFUL0lGHA.4772@xxxxxxxxxxxxxxxxxxxxxxx
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?
No this works just the same in 2005. Perhaps you could post a script that reproduces your problem.
David
.
- 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]
- Re: sql2k5 security
- From: param
- sql2k5 security
- Prev by Date: Re: SQL2005 security
- Next by Date: Re: LINKED server problem..
- Previous by thread: Re: sql2k5 security
- Next by thread: Re: sql2k5 security
- Index(es):