﻿<?xml version="1.0" encoding="utf-8"?><rss xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" version="2.0"><channel><title>SQLServerCentral.com Content tagged Security, Schema</title><link>http://www.sqlservercentral.com/</link><description>Content tagged Security, Schema posted on SQLServerCentral.com</description><language>en-us</language><ttl>360</ttl><managingEditor>sjones@sqlservercentral.com (Steve Jones)</managingEditor><item><title>Breaking ownership chaining within a schema in SQL Server</title><description><![CDATA[<p>I have several objects, all in the same schema. Because of this, ownership chaining is working, as described in this previous tip. However, I don't want ownership chaining to be on, but I need the objects to remain in the same schema. How can I do this?</p>]]></description><guid>http://www.sqlservercentral.com/redirect/articles/67825/</guid><pubDate>Fri, 21 Aug 2009 06:00:00 UT</pubDate><link>http://www.sqlservercentral.com/redirect/articles/67825/</link></item><item><title>Granting limited permissions to create views in another schema in SQL Server - Part 2  </title><description><![CDATA[<p>In a previous tip, Granting limited permissions to create views in another schema in SQL Server, I showed how to use the CREATE VIEW permission and the ALTER SCHEMA permission to allow users to create new views using the same schema as the tables. However, I have found that the users can alter and drop tables in this schema which is beyond what I want them to do. A DENY CREATE TABLE does not work, so what can I do to prevent them from touching the tables in this way? In this tip I will show you how you can use a DDL trigger to prevent this unneeded access.</p>]]></description><guid>http://www.sqlservercentral.com/redirect/articles/67739/</guid><pubDate>Mon, 17 Aug 2009 06:00:00 UT</pubDate><link>http://www.sqlservercentral.com/redirect/articles/67739/</link></item></channel></rss>