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

6,169 reads

Blogs

A New Word: Foilsick

By

foilsick – adj. feeling ashamed after revealing a little too much of yourself to...

Accelerated Database Recovery for tempdb in SQL Server 2025

By

Accelerated database recovery was introduced in SQL Server 2019 and provides fast recovery, instantaneous...

Measuring What Matters: Operationalizing Data Trust for CDOs

By

Trust is the currency of the data economy. Without it, even the most advanced...

Read the latest Blogs

Forums

Create an HTML Report on the Status of SQL Server Agent Jobs

By Nisarg Upadhyay

Comments posted to this topic are about the item Create an HTML Report on...

ETL Framework In Production

By Rahulmsb5

Hello, I am leveraging Python within SQL Server Integration Services (SSIS) packages, primarily through...

SQL Server Ghosts

By Steve Jones - SSC Editor

Comments posted to this topic are about the item SQL Server Ghosts

Visit the forum

Question of the Day

SQL Server Ghosts

For Halloween, what are ghost records?

See possible answers