Home > Blogs > Schemas as Security Boundaries

Schemas as Security Boundaries

By  Aug 3, 2010

Topics: SQL Server, Data

There was a question yesterday on Twitter (hashtag #sqlhelp) wondering how to let developers create stored procedures and then grant the rights to those procedures to other people. I believe that question got answered, but it also brought up the subject of Schemas, which I've blogged about before.

Schemas can act both as a container and a security boundary. That means you can combine a role and schema in SQL Server to create an "area" or bucket of things you want the developer to have full control over, without having to make them a full database owner. I would show you that process here, complete with an example and so on - but happily theSQL Server best practices team beat me to it. Check this link, and move to the middle of the page - where it starts with "Using Schemas in SQL Server": http://msdn.microsoft.com/en-us/library/dd283095(SQL.100).aspx 

Yet another great reason to learn and use schemas...