Articles

External Article

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.

2009-08-17

3,444 reads

Blogs

Using CAT for Testing of Data Agents

By

In last months one of the scenarios where you can use AI has been...

Are you getting value from your reporting?

By

Do you spend so long manipulating your data into something vaguely useful that you...

The Book of Redgate: SQL Server Central

By

It was neat to stumble on this in the book, a piece by me,...

Read the latest Blogs

Forums

Foreach Loop still executes after process and delete all the folders

By robink

I have two challenges XML source control not displaying the XML file parent node...

Which 'Where' statement conditional upon a variable

By DaveBriCam

Thanks in advance for any clues on this. I am trying to write a...

Backup to Immutable Storage

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Backup to Immutable Storage

Visit the forum

Question of the Day

Backup to Immutable Storage

In SQL Server 2025, a backup can be made on Azure Immutable Storage. What changes in how the backup is created?

See possible answers