Skip to content

Commit 3c2dbd3

Browse files
authored
Merge pull request #15627 from WilliamAntonRohm/issue-4983
sql-docs/issues/4983 -- code fence errors
2 parents d8a5e20 + 1c647ab commit 3c2dbd3

1 file changed

Lines changed: 8 additions & 7 deletions

File tree

docs/linux/sql-server-linux-security-get-started.md

Lines changed: 8 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -82,7 +82,7 @@ GRANT SELECT ON Object::Sales TO Orders;  
8282
GRANT UPDATE ON Object::Sales TO Orders;  
8383
GRANT DELETE ON Object::Sales TO Orders;  
8484
ALTER ROLE Sales ADD MEMBER Jerry;  
85-
```  
85+
```
8686

8787
For more information about the permission system, see [Getting Started with Database Engine Permissions](../relational-databases/security/authentication-access/getting-started-with-database-engine-permissions.md).
8888

@@ -102,14 +102,14 @@ GO  
102102
CREATE USER Manager WITHOUT LOGIN;    
103103
104104
CREATE USER SalesPerson280 WITHOUT LOGIN;   
105-
```  
105+
```
106106

107107
Grant read access on the `Sales.SalesOrderHeader` table to both users:   
108108

109109
```  
110110
GRANT SELECT ON Sales.SalesOrderHeader TO Manager;     
111-
GRANT SELECT ON Sales.SalesOrderHeader TO SalesPerson280;  
112-
```  
111+
GRANT SELECT ON Sales.SalesOrderHeader TO SalesPerson280;
112+
```
113113

114114
Create a new schema and inline table-valued function. The function returns 1 when a row in the `SalesPersonID` column matches the ID of a `SalesPerson` login or if the user executing the query is the Manager user.
115115

@@ -124,7 +124,7 @@ AS
124124
RETURN SELECT 1 AS fn_securitypredicate_result
125125
WHERE ('SalesPerson' + CAST(@SalesPersonId as VARCHAR(16)) = USER_NAME())
126126
OR (USER_NAME() = 'Manager');   
127-
```  
127+
```
128128

129129
Create a security policy adding the function as both a filter and a block predicate on the table:
130130

@@ -250,11 +250,12 @@ For more information about TDE, see [Transparent Data Encryption (TDE)](../relat
250250
## Configure backup encryption
251251
SQL Server has the ability to encrypt the data while creating a backup. By specifying the encryption algorithm and the encryptor (a certificate or asymmetric key) when creating a backup, you can create an encrypted backup file.    
252252

253-
> [!WARNING]  
254-
> It is very important to back up the certificate or asymmetric key, and preferably to a different location than the backup file it was used to encrypt. Without the certificate or asymmetric key, you cannot restore the backup, rendering the backup file unusable.
253+
> [!WARNING]
254+
> It is very important to back up the certificate or asymmetric key, and preferably to a different location than the backup file it was used to encrypt. Without the certificate or asymmetric key, you cannot restore the backup, rendering the backup file unusable.
255255
256256

257257
The following example creates a certificate, and then creates a backup protected by the certificate.
258+
258259
```
259260
USE master;  
260261
GO  

0 commit comments

Comments
 (0)