Re: Developers and prod servers
From: Paul (Paul.no.spam.please.Schlieper@communication.gc.ca)
Date: 03/12/03
- Next message: SQL Server Development Team [MSFT]: "Re: Monitor message: running low on memory"
- Previous message: Gert E.R. Drapers: "Re: xp_qv -- Extended Stored Procedure"
- In reply to: Dan Guzman: "Re: Developers and prod servers"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
From: "Paul" <Paul.no.spam.please.Schlieper@communication.gc.ca> Date: Wed, 12 Mar 2003 09:04:12 -0800
Hi Dan,
Thanks for the reply, that's what I wanted to know.
Paul
>-----Original Message-----
>You can add them to the db_datareader role in the desired
databases.
>They will not be able to create database objects as long
as you haven't
>granted them CREATE permissions or added them to the sysadmin,
>db_ddladmin or db_owner roles. Note that members of the local
>administrators group are sysadmin role members by default.
>
>--
>Hope this helps.
>
>Dan Guzman
>SQL Server MVP
>
>-----------------------
>SQL FAQ links (courtesy Neil Pike):
>
>http://www.ntfaq.com/Articles/Index.cfm?DepartmentID=800
>http://www.sqlserverfaq.com
>http://www.mssqlserver.com/faq
>-----------------------
>
>"Paul" <paul.no.spam.please.Schlieper@communication.gc.ca>
wrote in
>message news:07dc01c2e8ac$a051ce90$a501280a@phx.gbl...
>> Hi,
>>
>> Using SQL2K on Win2K.
>>
>> How do I go about granting my developers read-access to the
>> production servers, but prevent them from changing stored
>> proc code on said servers? I only want them to be able to
>> create sprocs on dev boxes.
>>
>> TIA,
>>
>> Paul
>>
>>
>
>
>.
>
- Next message: SQL Server Development Team [MSFT]: "Re: Monitor message: running low on memory"
- Previous message: Gert E.R. Drapers: "Re: xp_qv -- Extended Stored Procedure"
- In reply to: Dan Guzman: "Re: Developers and prod servers"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|