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

Blogs

Creating a GitHub Actions Self-Hosted Runner

By

I had to demo the Flyway Autopilot system recently and created a GitHub Actions...

Migrating from Azure PG Single Server to Flex with Azure VM and pg_dump/restore

By

This is more complicated than using the Azure Migration method, but because it’s maxed...

PowerShell (and T-SQL) and Elastic Jobs

By

I’ve covered how to create Elastic Jobs in the portal (this one is important...

Read the latest Blogs

Forums

Contracting DBA - Permissions for initial analysis

By StephenSQL

Accidental DBA here.  After looking at all the work that needs to be done,...

How to convert run_date and run_time columns to datetime from SQL Agent systable

By Lord Slaagh

Hello SSC, Hope you are all having a great Monday! I am trying to...

SQL Server Reporting Services 2022 Permissions Issue

By benkaz

I'm having a bit of an issue with SSRS permissions. Users (Operations Manager Report...

Visit the forum

Question of the Day

AG Rules for Databases

Which of these is not a requirement for a database to be added to an Availability Group (AG)?

See possible answers