http://sqlblog.com/blogs/buck_woody/archive/tags/Schemas/default.aspxTags: SchemasenCommunityServer 2.1 SP2 (Build: 61129.1)http://sqlblog.com/blogs/buck_woody/archive/2010/08/03/schemas-as-security-boundaries.aspxTue, 03 Aug 2010 13:00:25 GMT21093a07-8b3d-42db-8cbf-3350fcbf5496:27563BuckWoody0http://sqlblog.com/blogs/buck_woody/comments/27563.aspxhttp://sqlblog.com/blogs/buck_woody/commentrss.aspx?PostID=27563<p>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. </p> <p>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": <a href="http://msdn.microsoft.com/en-us/library/dd283095(SQL.100).aspx">http://msdn.microsoft.com/en-us/library/dd283095(SQL.100).aspx</a>&nbsp;</p> <p>Yet another great reason to learn and use schemas...</p><img src="http://sqlblog.com/aggbug.aspx?PostID=27563" width="1" height="1">SQL ServerSecuritySchemas