Permissions required to create procedures
-
What role(s) does a developer need to create a stored procedure?
In the past we have assigned developers to the dbo role but we are tightening our security and I want to limit what the developer can do in a new database.
Thanks
Jeremy
-
Would this help
Fixed database role Description db_owner Performs the activities of all database roles, as well as other maintenance and configuration activities in the database. The permissions of this role span all of the other fixed database roles. db_accessadmin Adds or removes Windows NT 4.0 or Windows 2000 groups and users, and SQL Server users in the database. db_datareader Sees all data from all user tables in the database. db_datawriter Adds, changes, or deletes data from all user tables in the database. db_ddladmin Adds, modifies, or drops objects in the database (runs all DDLs). db_securityadmin Manages roles and members of SQL Server 2000 database roles, and manages statement and object permissions in the database. db_backupoperator Has permission to back up the database. db_denydatareader Denies permission to select data in the database. db_denydatawriter Denies permission to change data in the database. So, I would say ddl_admin
--
Frank Kalis
Microsoft SQL Server MVP
Webmaster: http://www.insidesql.org/blogs
My blog: http://www.insidesql.org/blogs/frankkalis/[/url] -
I must have an old version of BOL
. This is what mine says for db_ddladmin:db_ddladmin Can issue ALL DDL, but cannot issue GRANT, REVOKE, or DENY statements. I'll try that and see what happens - thanks.
Jeremy
-
I looked at roles-SQL Server, predefined. It's not impossible that both statement appear in BOL
--
Frank Kalis
Microsoft SQL Server MVP
Webmaster: http://www.insidesql.org/blogs
My blog: http://www.insidesql.org/blogs/frankkalis/[/url]
Viewing 4 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply