Ownership chaining

Stairway to SQL Server Security

Stairway to SQL Server Security Level 7: Security Across Databases with Cross-Database Ownership Chaining

  • Stairway Step

Sometimes you need to reach outside a database and access data and objects from multiple databases, which raises some security issues and increases the complexity of data access. In this stairway level, you’ll learn about cross-database ownership chaining so that you can reach across database boundaries securely.

5 (2)

You rated this post out of 5. Change rating

2024-02-23 (first published: )

9,709 reads

Blogs

Friday Flyway Tips–Quick Command Line Access

By

One of the things I had to do recently in a demo was access...

A New Word: Aesthosis

By

aesthosis– n. the state of feeling trapped inside your own subjective tastes – not...

A First Look at Redgate’s Subsetter

By

I have been a proponent of subsetting databases in dev/test for a long time....

Read the latest Blogs

Forums

Frustrated trying to get Cross DB Access by Signing SP with Certificate

By Ken McKelvey

Maybe it is lack of caffeine, but I cannot see why the following test...

SSIS Execute Package Fail in SSMS but Agent Job Succeeds

By jerryszz

Hello, I created a SSIS package to transfer data from an XML file to...

Cyber Insurance for War

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Cyber Insurance for War

Visit the forum

Question of the Day

Writing to Clones

I run this code on SQL Server 2019:

DBCC CLONEDATABASE(imdb, imdb_dev)
I then change to the cloned database, imdb_dev, and run some queries. I then run this code while testing:
INSERT dbo.Title (TitleID, Title, DateReleased) VALUES (3234, 'Maestro', '2023')
GO
What happens?

See possible answers