Granting limited permissions to create views in another schema in SQL Server - Part 2

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.

Loyalty Cards

Many businesses have loyalty programs to encourage repeat business. However do they think about data security when they build these programs? Steve Jones thinks they could do better.

Loyalty Cards

Many businesses have loyalty programs to encourage repeat business. However do they think about data security when they build these programs? Steve Jones thinks they could do better.

Loyalty Cards

Many businesses have loyalty programs to encourage repeat business. However do they think about data security when they build these programs? Steve Jones thinks they could do better.

Loyalty Cards

Many businesses have loyalty programs to encourage repeat business. However do they think about data security when they build these programs? Steve Jones thinks they could do better.

Placing a Value on Data

What's your stolen data worth? It might be worth investigating, as Steve Jones suggests. Then you'll know how much you should be spending to protect it.

Placing a Value on Data

What's your stolen data worth? It might be worth investigating, as Steve Jones suggests. Then you'll know how much you should be spending to protect it.

Placing a Value on Data

What's your stolen data worth? It might be worth investigating, as Steve Jones suggests. Then you'll know how much you should be spending to protect it.

Placing a Value on Data

What's your stolen data worth? It might be worth investigating, as Steve Jones suggests. Then you'll know how much you should be spending to protect it.

SQL 2008 - SSMS