Re: Limiting access to SQL Server 2000 for our junior developers
Date: 8 Aug 2005 23:01:45 -0700
Thanks for the quick response :-)
I would assume that because database roles are created per database, I
would have do this on all 25 db's?
Dandy Weyn [Dandyman] wrote:
> Create a database role
> grant the role data_reader permission
> grant the role data_writer permission
> grant the role the CREATE TABLE permission
> deny the role DELETE Permission on any object
> Dandy Weyn
> Check my SQL Server Resource Pages at http://www.dandyman.net/sql
> <email@example.com> wrote in message
> > Hi All
> > I've been given a task to lockdown access to our database server to our
> > 6 junior developers. We currently have about 25 databases on our SQL
> > Server. I'm trying to do the following the easiest way:
> > 1. Create six separate logins
> > 2. For all 25 db's only allow selects, inserts and updates for them to
> > all tables.
> > 3. They must be able to create tables but not drop or truncate
> > anything.
> > 4. Of course no access to the master db
> > 5. Lock out all dangerous sp's like xp_cmdshell
> > I'm new to SQL permissions. What would be the easiest way to doing
> > this without manually adding all the permissions table level for each
> > login?
> > Thanks in advance for any help.
> > Bill