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.
2024-05-08 (first published: 2015-04-08)
11,282 reads
Even an otherwise well-secured database is susceptible to attack if an attacker is able to get access to the disk files that comprise the database. Cell-level encryption can protect some of the data, but for complete protection against this kind of attack it is necessary to encrypt the files and not just the data. That is exactly what Transparent Data Encryption (TDE) does, and in this stairway level you'll learn what TDE does, how it works, and how to make use of it to protect your database files.
2023-03-15 (first published: 2015-06-03)
6,416 reads
By defining server- and database-level audits, you can record just about any kind of event that occurs in SQL Server, which can be an invaluable source of security troubleshooting and forensic information when security breaches occur. In this stairway level you’ll learn how to define the various audit specification objects, how to capture audit data, and how to explore and use the data.
2023-03-08 (first published: 2015-09-23)
8,586 reads
A permission gives a principal access to an object to perform certain actions on or with the object. SQL Server has a mind-numbingly huge number of permissions that you can grant to a principal, and you can even deny or revoke those permissions. This sounds a bit complicated, but by the end of this stairway level you’ll understand how SQL Server permissions work and how you can exert very granular control over object creation, data access, and other types of actions on database and server objects.
2022-09-28 (first published: 2014-10-15)
9,738 reads
In this stairway level you’ll learn how you can give principals access to groups of objects by assigning permissions on schemas instead of individual tables, code modules, and other objects. You’ll also learn about the benefits of user-schema separation and how it can increase object security, and how using default schemas for users and groups can simplify object access management and security.
2022-09-21 (first published: 2014-12-03)
12,372 reads
Authentication is the first step in letting a principal get access to an instance of SQL Server, essentially resolving the question, Who are you? In this stairway level you’ll learn about the basics of authentication and the authentication options available. This level covers logins and users and you’ll learn about the password policies that can help strengthen SQL Server authentication.
2021-03-17 (first published: 2014-06-18)
10,368 reads
What is a SQL Server principal? And what does it get a permission on? In this stairway level, you’ll learn about the various principals that can be authorized through permissions to perform actions and access securable objects in the SQL Server instance.
2019-08-21 (first published: 2014-07-16)
11,812 reads
The ubiquity of databases and the potentially valuable information stored in them makes them attractive targets for people who want to steal data or harm its owner by tampering with it. Making sure that your data is secure is a critical part of configuring SQL Server and developing applications that use it to store data.
2019-08-07 (first published: 2014-06-04)
14,944 reads
Unlike some other industrial-strength database servers, SQL Server lacks a built-in mechanism for protecting individual data records, called row-level security. This stairway level explores why you might want to use such a low-level granularity of data access security and how you can implement row-level security.
2015-07-29
6,428 reads
This stairway level will explore data protection through encryption, both when the data is in motion across the network or in memory and at rest in a table. You’ll learn about the encryption key hierarchy and the various kinds of keys you can use to encrypt data, as well as how you can manage the keys or let SQL Server do it for you.
2015-04-15
7,648 reads
By Brian Kelley
Tech conferences aren't just for networking and learning how to address a problem you're...
By DataOnWheels
When I created the website on WordPress, I was expecting all the features I...
By Steve Jones
I wrote a piece on the new SUBSTRING in SQL Server 2025 and got...
I changed my email address in Edit Profile page, but it has no effect...
Comments posted to this topic are about the item The case for "Understanding our...
Comments posted to this topic are about the item Specifying the Collation
I am dealing with issues on my SQL Server 2022 instance related to collation. I have an instance collation of Latin1_General_CS_AS_KS_WS, but a database collation of Latin1_General_CI_AS. I want to force a few queries to run with a specified collation by using code like this:
DECLARE @c VARCHAR(20) = 'Latin1_General_CI_AS'
SELECT p.PersonType,
p.Title,
p.LastName,
c.CustomerID,
c.AccountNumber
FROM Person.Person AS p
INNER JOIN Sales.Customer AS c
ON c.PersonID = p.BusinessEntityID
COLLATE @c
Will this solve my problem? See possible answers