Re: Sql Server - Basic Permissions Question
- From: "Arnie Rowland" <arnie@xxxxxxxx>
- Date: Mon, 28 Aug 2006 07:31:14 -0700
You are making very good choices. A good security model includes adding all
users to both db_denyReader and db_denyWriter, and providing ALL data access
through Stored Procedures.
On cravat is to be sure that all tables and stored procedures are 'owned' by
the dbo schema. Make a practice of always adding 'dbo.' to the object name
in the create scripts. (e.g., CREATE PROCEDURE dbo.MyStoredProcedure)
--
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"Ranginald" <davidwank@xxxxxxxxx> wrote in message
news:1156718450.101845.48600@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
I have a SQL Server database and I want a user to be able to execute
stored procedures only. These stored procedures use SELECT and WHERE
statements and return integers.
I have set EXECUTE permissions to the sp's as needed for the user.
It is possible to allow a user to have EXECUTE permissions on the sp's,
but deny everything else? E.g. If id did denyreader and allowed
EXECUTE on the sp's, would the command fail because the sp's have
SELECT and WHERE statements?
Thanks!
-Ranginald
.
- References:
- Sql Server - Basic Permissions Question
- From: Ranginald
- Sql Server - Basic Permissions Question
- Prev by Date: Re: SQL Server 2005: Checking if Login is connected to any databas
- Next by Date: Re: Delegation through Linked Server Stops working
- Previous by thread: Re: Sql Server - Basic Permissions Question
- Next by thread: RE: Login has all rigfhts but can login to sql
- Index(es):
Relevant Pages
|
|