Re: Logins & Permissions
- From: Ekrem Önsoy <ekrem@xxxxxxxxxxxx>
- Date: Wed, 10 Sep 2008 11:23:37 +0300
Well, actually I'd like to correct some terminology here. At server level, we use "Logins" (SQL \ Windows) to connect to a SQL Server Instance and perform server level jobs. At database level, "Users" are used and these users are mapped to Logins.
I think you first better review Fixed Roles (Server Level), Database roles (Database Level) and Permissions and their hierarcy of course. Then you'll have enough idea about configuring your permisson security.
You can start with BOL, it'll help you a lot : http://msdn.microsoft.com/en-us/library/ms187648(SQL.90).aspx
--
Ekrem Önsoy
"Phil" <Phil@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:75BCC419-E3AD-45B7-90D5-F0E3E3335C17@xxxxxxxxxxxxxxxx
Hi,
I am using SQL Server 2005 on a Windows NT Network
This is not something that I have really had little to deal with in the past
but I am trying to get some understanding of logins and permissions, I know
that you can have either a SQL Server Login or a Windows Login and a Windows
one is what I am currently using and this allows you rights to do certain
things with the SQL Server and then you have logins for the databases which
give you access to do certain things within the databases, well that is what
I think it all does, but what I want to do is restric people from only being
able to run a stored procedure and view its results either through Query
Analyser or Crystal Reports but not allow them to alter the stored procedure,
if someone could offer me some advice on this and where I can find some basic
white papers or web sites that explain the basics of SQL Logins and
Permissions it would be much appreciated.
Thanks
tress
.
- References:
- Logins & Permissions
- From: Phil
- Logins & Permissions
- Prev by Date: Logins & Permissions
- Next by Date: block access to fileds
- Previous by thread: Logins & Permissions
- Next by thread: block access to fileds
- Index(es):
Relevant Pages
|