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,248 reads

Blogs

SQL Server instance metadata inventory with PowerShell and SMO

By

SQL Server instance metadata inventory with PowerShell and SMO The purpose...

5 SQL Tricks Worth Remembering Before You Close the Laptop

By

Disclosure: this post may contain links to books as an affiliate link. If you...

Google – NotebookLM on ThakurVinay blog

By

Google has contributed a lot of stuff/enhancement on its portfolio, google is no longer...

Read the latest Blogs

Forums

Celebrating 30 years of PostgreSQL, A Thank you message

By Pat Wright

Comments posted to this topic are about the item Celebrating 30 years of PostgreSQL,...

provisioning sql server via VMware Cloud Foundation

By andreas.kreuzberg

Hello, has anyone here ever provisioned and actually used an MS SQL Server with...

No More Deadlocks

By Steve Jones - SSC Editor

Comments posted to this topic are about the item No More Deadlocks

Visit the forum

Question of the Day

No More Deadlocks

After detecting deadlocks in SQL Server 2025 and lowering the time threshold for detecting future issues, when does the Database Engine return to the 5s default interval?

See possible answers