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.

Blogs

The 2026 Redgate Summit in New York City

By

We’re coming back to New York, which is exciting for me. I love NYC....

Monitoring Fabric Mirroring for SQL 2025

By

I previously wrote about how the underlying technology for Fabric mirroring changed with SQL...

Monday Monitor Tips: Intelligent Alert Thresholds

By

At the recent Redgate Summit in Chicago, I demo’d (lightly) the ML based Alert...

Read the latest Blogs

Forums

Seeding a Fabric Warehouse with dbt for Visual Studio Code: The Fabric Modern Data Platform

By John Miner

Comments posted to this topic are about the item Seeding a Fabric Warehouse with...

Seeding a Fabric Warehouse with dbt for Visual Studio Code: The Fabric Modern Data Platform

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Seeding a Fabric Warehouse with...

Doing the Little Things

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Doing the Little Things

Visit the forum

Question of the Day

Historical Data Tracking

If I want to track historical data values, which mechanism should I use?

See possible answers