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

Claude finds two cryptographic weaknesses (but the sky isn’t falling)

By

If you haven't seen the announcement, Anthropic was able to utilize Claude (Mythos Preview)...

Generate Embeddings in SQL with Aurora and Bedrock

By

Most embedding pipelines on AWS have the same shape: a job reads rows out...

Resolving SQL Server Transaction Log Issues Efficiently

By

Transaction log issues are one of the quietest ways a healthy database turns into...

Read the latest Blogs

Forums

Symmetric Key Encryption

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Symmetric Key Encryption

The “Successful Login” Dilemma: Why Your Login Auditing Strategy Might Be Hurting Your Server

By Pablo Echeverria

Comments posted to this topic are about the item The “Successful Login” Dilemma: Why...

Building Your Own Software

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Building Your Own Software

Visit the forum

Question of the Day

Symmetric Key Encryption

If I run this statement in SQL Server 2025, how is the password encrypted? 

CREATE SYMMETRIC KEY MySymmetricKey
WITH ALGORITHM = AES_256,
KEY_SOURCE = 'My secret key source passphrase',
IDENTITY_VALUE = 'My secret identity value'
ENCRYPTION BY PASSWORD = 'S&perS#cretP@ssword7';
GO

See possible answers