SQL Server 2005 Stored Procedure security annoyances
- From: sune42@xxxxxxxxxxx
- Date: 17 Sep 2006 02:52:20 -0700
hi
I have came to the maturity level to stop using the sa account when I
run
my web-server.
So, I created a new account and added it to the DB_datareader/writer
role.
but I still can't execute my own stored procedures.
Are there no way to set per database the rights to execute non-system
stored proecedure on a database wide level?
I mean it is unrealistic to have to manually set for each SP the rights
because
I am sure I will forget some SP's and probably forget to set the rights
when
I add new SP's in the future. Sure , I can run some wierd query to set
the
rights to all SP's, but that's a pain to lookup as well.
I mean it must be possible to set the SP security settings with minimal
time/effort,
otherwise I can just as well continiue using a account with to broad
rights. db_owner?
We need a default DB_ExecuteSP role that each user can be associated
with!
any ideas?
/andy
.
- Follow-Ups:
- Re: SQL Server 2005 Stored Procedure security annoyances
- From: Dan Guzman
- Re: SQL Server 2005 Stored Procedure security annoyances
- From: Uri Dimant
- Re: SQL Server 2005 Stored Procedure security annoyances
- Prev by Date: Re: Lis of all logins?
- Next by Date: Re: SQL Server 2005 Stored Procedure security annoyances
- Previous by thread: Lis of all logins?
- Next by thread: Re: SQL Server 2005 Stored Procedure security annoyances
- Index(es):
Relevant Pages
|
|
