Security

External Article

How to Get SQL Server Security Horribly Wrong

  • Article

It is no good doing some or most of the aspects of SQL Server security right. You have to get them all right, because any effective penetration of your security is likely to spell disaster. If you fail in any of the ways that Robert Sheldon lists and describes, then you can't assume that your data is secure, and things are likely to go horribly wrong.

2015-05-13

9,527 reads

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.

(3)

You rated this post out of 5. Change rating

2024-05-08 (first published: )

11,357 reads

Blogs

Audit – Security Compliance Frameworks (Part 1)

By

This blog series on Audit/Compliance/Security, this is first blog where we would discuss about...

Restore SQL Server Database to an OrbStack Container

By

In the previous post, we've built a SQL Server 2025 sandbox in an OrbStack...

Day of Data Baton Rouge Slides and Code

By

Thanks to everyone for attending my talk today at Day of data Baton Rouge...

Read the latest Blogs

Forums

Can You Really Downgrade from Enterprise to Standard and Save Thousands? Here's What Happened

By Pablo Echeverria

Comments posted to this topic are about the item Can You Really Downgrade from...

What is CPU Usage?

By Steve Jones - SSC Editor

Comments posted to this topic are about the item What is CPU Usage?

Limiting Checkpoints

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Limiting Checkpoints

Visit the forum

Question of the Day

Limiting Checkpoints

If I use the -k parameter with a number after it, what does this change in SQL Server?

See possible answers