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

Database AI Agents: The Read-Only Rule

By

Fourth in a series on Ai and databases. What Read-Only Advisory Actually Means A...

Creating a SQL Stored Procedure to Load a SCD2

By

This is a blog that I am writing for future me and hopefully it’ll...

Funny Money: #SQLNewBlogger

By

While wandering around the documentation looking for some Question of the Day topics, I...

Read the latest Blogs

Forums

Backup Availability Group

By jayoub

Please I am hoping for some feedback Specifications: Windows Server 2022 SQL Server 2022...

How Do the Experts Become Experts?

By Kathi Kellenberger

Comments posted to this topic are about the item How Do the Experts Become...

Stairway to Reliable Database Deployments Level 4 – Preparing for Production Deployment

By Massimo Preitano

Comments posted to this topic are about the item Stairway to Reliable Database Deployments...

Visit the forum

Question of the Day

Running SQLCMD II

I run this command to start SQLCMD:

sqlcmd -S localhost -E -c "proceed"
At the prompt, I type this (the 1> and 2> are prompts):
1> select @@version
2> go
What happens?

See possible answers