SP_EXECUTESQL Security in 2005
- From: DigHazuse <DigHazuse@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 26 Feb 2008 08:44:01 -0800
Hi,
Recently moved a few DBs from '00 to '05. At that time our DBA changed the
security to all SP's so that the impersonating user only has access to
Execute the SP's. This seemed all fine and dandy, except that some of our
SP's had dynamic SQL using SP_EXECUTESQL, which fail on security when
executed.
She would like me to change all the SP's to not be dynamic (which, in these
cases, would not make sense).
I understand what she is trying to do, but it seems silly, to me, to not be
able to use SP_EXECUTESQL when "necessary".
Is there a way, security wise (or something else outside the range of my
question) to meet in the middle or is there a way to change my SP to be able
to accomplish the same functionality?
Thank you
t
.
- Follow-Ups:
- Re: SP_EXECUTESQL Security in 2005
- From: Andrew J. Kelly
- Re: SP_EXECUTESQL Security in 2005
- Prev by Date: LOGON trigger
- Next by Date: Re: SP_EXECUTESQL Security in 2005
- Previous by thread: LOGON trigger
- Next by thread: Re: SP_EXECUTESQL Security in 2005
- Index(es):
Relevant Pages
|
|
