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

Blogs

SQL Server Wait Stats

By

Everything in SQL Server is waiting for something…this is by design. And most people...

FabCon 2025 Recap

By

Hey fellow data friends! Wow, March was an absolutely crazy month (in the best...

Privacy Policy

By

We value your privacy. This policy explains what personal data we collect and why. What...

Read the latest Blogs

Forums

XML data import with poor stored procedure performance (needs optimization)

By Lord Slaagh

Hello SSC! I have been tasked with optimizing a stored procedure the imports data...

Trouble accessing hidden XML download link on Blazor-based government site

By Jobs90312

Hey everyone, I'm trying to access an XML file download from a government website...

Index is only used for statistics in query plan

By michel.zdw

Hi, I have very large table (6 * 10^9 records) where i have 4...

Visit the forum

Question of the Day

Importing Flat Files

What types of sources can be used with the Import Flat File Wizard in SQL Server Management Studio (SSMS)?

See possible answers