SQL Server script grants permissions to users

Here's a simple script that can be customized to quickly grant permissions to various users on all tables or stored procedures. Using this script I was able to reduce the time taken to grant permissions during installation from 30 minutes to 1 second! It is much faster than manually checking boxes next to each table using the Manage Permissions GUI provided in SQL Server. It has been tested on SQL Server 2000.

In this example, I have two users:

  1. test_user has all permissions on all tables
  2. test_reader has only read permission on all tables

Here is the script:

create proc pr_GrantPermissions
-- script to grant permissions on all user defined tables and 
-- stored procedures to test_user and test_reader

-- grant all on all tables to test_user
print 'Granting table Permissions ...'
DECLARE tnames_cursor CURSOR
   SELECT name from sysobjects where xtype='U'

OPEN tnames_cursor
DECLARE @tablename sysname
FETCH NEXT FROM tnames_cursor INTO @tablename
   IF (@@FETCH_STATUS <> -2)
      SELECT @tablename = RTRIM(@tablename) 
      EXEC ('GRANT ALL ON ' + @tablename + ' TO test_User')
      EXEC ('GRANT SELECT ON ' + @tablename + ' TO test_Reader') 
   FETCH NEXT FROM tnames_cursor INTO @tablename
CLOSE tnames_cursor
DEALLOCATE tnames_cursor

print 'Granting procedure Permissions ...'

-- grant exec on all procedures to test_user and test_reader
DECLARE proc_names_cursor

    Requires Free Membership to View

CURSOR FOR SELECT name from sysobjects where xtype='P' OPEN proc_names_cursor DECLARE @procname sysname FETCH NEXT FROM proc_names_cursor INTO @procname WHILE (@@FETCH_STATUS <> -1) BEGIN IF (@@FETCH_STATUS <> -2) BEGIN SELECT @procname = RTRIM(@procname) EXEC ('GRANT ALL ON ' + @procname + ' TO test_User, Test_Reader ') END FETCH NEXT FROM proc_names_cursor INTO @procname END CLOSE proc_names_cursor DEALLOCATE proc_names_cursor print '*********************************************' print 'All permissions granted'

For More Information

  • Feedback: E-mail the editor with your thoughts about this tip.
  • More tips: Hundreds of free SQL Server tips and scripts.
  • Tip contest: Have a SQL Server tip to offer your fellow DBAs and developers? The best tips submitted will receive a cool prize -- submit your tip today!
  • Ask the Experts: Our SQL, database design, Oracle, SQL Server, DB2, metadata, and data warehousing gurus are waiting to answer your toughest questions.
  • Forums: Ask your technical SQL Server questions--or help out your peers by answering them--in our active forums.
  • Best Web Links: SQL Server tips, tutorials, and scripts from around the Web.

This was first published in June 2003

There are Comments. Add yours.

TIP: Want to include a code block in your comment? Use <pre> or <code> tags around the desired text. Ex: <code>insert code</code>

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
Sort by: OldestNewest

Forgot Password?

No problem! Submit your e-mail address below. We'll send you an email containing your password.

Your password has been sent to:

Disclaimer: Our Tips Exchange is a forum for you to share technical advice and expertise with your peers and to learn from other enterprise IT professionals. TechTarget provides the infrastructure to facilitate this sharing of information. However, we cannot guarantee the accuracy or validity of the material submitted. You agree that your use of the Ask The Expert services and your reliance on any questions, answers, information or other materials received through this Web site is at your own risk.