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

Blogs

The DIY Cost of Masking Test Data For Smaller Organizations

By

One of the things I’ve tried hard to do in database development situations if...

T-SQL Tuesday #196 – Two risky career decisions I made

By

The T-SQL Tuesday topic this month comes James Serra. What career risks have you...

T-SQL Tuesday #192: What career risks have you taken?

By

This T-SQL Tuesday is hosted by the one and only James Serra – literally...

Read the latest Blogs

Forums

XACT_ABORT being set to ON by web services

By zoggling

We have two "identical" instances of an ASP.NET web service (or so I have...

OPENQUERY Flexibility

By Steve Jones - SSC Editor

Comments posted to this topic are about the item OPENQUERY Flexibility

A Full Shutdown

By Steve Jones - SSC Editor

Comments posted to this topic are about the item A Full Shutdown

Visit the forum

Question of the Day

OPENQUERY Flexibility

Which of these are valid OPENQUERY() uses?

See possible answers