Stairway to SQL Server Security

Stairway to SQL Server Security Level 6: Execution Context and Code Signing

A fundamental way that SQL Server determines whether a principal has the permissions necessary to execute code is with its execution context rules. It’s all complicated by the possibility that a principal has permission to execute code but doesn’t have permission on the underlying objects accessed by the code, such as the data in a table. This stairway level will explore SQL Server’s execution context, ownership chains, and impersonation, as well as show you how you can control access to data via T-SQL code.

You rated this post out of 5. Change rating

2015-02-04

5,832 reads

Blogs

Using Flyway with Feature Flags

By

There is a nice article at Harness.io on their use of feature flags and...

Microsoft Build event announcements on Fabric

By

There were a number of Microsoft Fabric announcements at Microsoft Build yesterday that I wanted to...

6 Can’t-Miss Basic SQL Courses to Learn in 2024: Your Fast Track to Data Mastery

By

Ready to dive into the world of SQL? Whether you're dreaming of a lucrative...

Read the latest Blogs

Forums

Monitoring if something is deleted in DB

By Martass

Hello, I have long-term task, which came one year ago, and just now I...

LOGON Trigger Count

By Steve Jones - SSC Editor

Comments posted to this topic are about the item LOGON Trigger Count

Invisible Downtime

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Invisible Downtime

Visit the forum

Question of the Day

LOGON Trigger Count

I have the need in SQL Server 2022 to create a complex set of checks for logins. I want to use Longon triggers, but I'd like to separate out logic. How many Logon Triggers can I create?

See possible answers