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

T-SQL Tuesday #198–Change Detection

By

This month we have a new host, Meagan Longoria, who graciously agreed to help...

Redgate and Rome

By

I’m at the UK Redgate office today, meeting with senior leaders in all areas...

Quick Tip: Check Most DTU Expensive Queries in Azure SQL Database

By

Optimizing Azure SQL Database performance often begins with identifying the most resource-intensive queries. Understanding...

Read the latest Blogs

Forums

Permissions Removal When Changing Object Schema

By Brandie Tarvin

When the schema of an object is changed, SQL Server wipes out the previous...

SSRS Is Dead. Here Are Your Real Options

By sgharlow

Comments posted to this topic are about the item SSRS Is Dead. Here Are...

The Distance Metric

By Steve Jones - SSC Editor

Comments posted to this topic are about the item The Distance Metric

Visit the forum

Question of the Day

The Distance Metric

In the new VECTOR_DISTANCE() function in SQL Server 2025, the first parameter is the distance_metric. What is this?

See possible answers