Permissions for database
From: Steve (smartin@cambridgeassociates.com)
Date: 08/22/02
- Next message: BP Margolin: "Re: Login with no Fixed Server Role and DB Role can stop SQL Agent Service?"
- Previous message: Steve: "Help: Login username and password"
- In reply to: Michel: "Permissions for database"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
From: "Steve" <smartin@cambridgeassociates.com> Date: Thu, 22 Aug 2002 13:53:34 -0700
This is a common problem. The best way I have found to
solve this problem is to use NT Authentication and roles.
It will also work with mixed mode security.
For each database, create a developer role and a Readonly
role (Can use public for this role too) For the owner of
the database, give that person dbo rights using
sp_ADDALIAS [User Login], 'dbo' (See Books on Line) This
would give that person(s) the right to create objects and
grant permissions for that object. The developers can be
given rights via the developer role which you can grant
Insert,Update,Delete,Select and Reference to and execute
for any stored procedures. For anyone using the
application, you can add them to the Readonly role which
should have select permissions and execute permissions.
Hope this helps
Steve
>-----Original Message-----
>Hi!
>We have several databases on SQL-Server with a number of
>developers. To define a user to access to a database we
>make him a local administrator on a server. We'd like to
>change this to something more useful as defining
>permissions for developers without making'em
>administrators. We tried to define login for a database,
>but it hasn't succeeded.
>We'd appretiate any help from you on the issue above.
>Thanks in advance.
>.
>
- Next message: BP Margolin: "Re: Login with no Fixed Server Role and DB Role can stop SQL Agent Service?"
- Previous message: Steve: "Help: Login username and password"
- In reply to: Michel: "Permissions for database"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
