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

Upgrading SQL Server Containers on the Laptop

By

I don’t have SQL Server installed on my laptop. In an effort to keep...

How to Find Expensive Queries in Amazon Redshift

By

Slow-running queries can degrade your Redshift cluster’s performance and lead to increased costs. Identifying...

The Notification Trap: How Input Fatigue Is Killing Deep Work in Tech

By

If you've been here before, you know this blog is usually about SQL Server,...

Read the latest Blogs

Forums

Wa cs Qlola bri

By advanceesthe

Butuh panduan penggunaan QLola BRI? Melalui whatsapp 08136035412 Butuh panduan penggunaan QLola BRI? Hubungi...

Layanan wa Qlola bri

By advanceesthe

Layanan support QLola BRI tersedia melalui WhatsApp 08136035412 untuk membantu berbagai kebutuhan Anda, mulai...

Pusat bantuan qlola bri resmi

By advanceesthe

Layanan bantuan QLola BRI melalui whatsapp 628136035412 Layanan bantuan QLola BRI kini lebih mudah...

Visit the forum

Question of the Day

How Long is a Long I/O?

In SQL Server 2025, a long I/O is recorded in the error log with message 833. How long much an I/O request be outstanding before this message is written to the log?

See possible answers