https://www.sqlserver70.com/tags/database-roles/Recent content in Database Roles on SQL Server ScriptsHugo -- gohugo.ioenSQLServer70.comFri, 08 Aug 2025 00:00:00 +0000https://www.sqlserver70.com/post/sql-server-object-level-permissions-script-generate-grant-statements-for-database-security/Fri, 08 Aug 2025 00:00:00 +0000https://www.sqlserver70.com/post/sql-server-object-level-permissions-script-generate-grant-statements-for-database-security/ <p>Giving an application role read, write and execute rights on a database usually means one <code>GRANT</code> per table per permission plus one per stored procedure, which runs to hundreds of statements on a mid-sized schema. The script below writes those statements for you from <code>sys.objects</code>, schema-qualified and bracket-quoted, so they can be reviewed and then run as one batch.</p> <script async src="https://pagead2.googlesyndication.com/pagead/js/adsbygoogle.js?client=ca-pub-1012089347386563" crossorigin="anonymous"></script> <ins class="adsbygoogle" style="display:inline-block;width:728px;height:90px" data-ad-client="ca-pub-1012089347386563" data-ad-slot="8593449130"></ins> <script> (adsbygoogle = window.adsbygoogle || []).push({}); </script> <h2 id="purpose-and-overview">Purpose and Overview</h2> <p>Setting up a new application role is the usual job-to-be-done here: a database role such as <code>SelectInsertUpdateDeleteExecSP</code> needs <code>SELECT</code>, <code>INSERT</code>, <code>UPDATE</code> and <code>DELETE</code> on the user tables and <code>EXECUTE</code> on the stored procedures, and nobody wants to type those by hand. Because the script only builds text, nothing changes until you copy its output into a query window and execute it, which makes it safe to run on production to see what it would do.</p>