Changes for page sql-tde

Last modified by Nikhil Singh on 2026/07/03 08:32
<
From version < 11.1 >
edited by Nikhil Singh
on 2026/07/03 08:30
To version < 6.2 >
edited by Rudi Marais
on 2025/02/26 16:00
>
Change comment: Added comment

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.nikhils
1 +XWiki.rudim
Content
... ... @@ -1,305 +1,282 @@
1 -= **1. Steps for Implementing Transparent Data Encryption (TDE) FROM SQL Server** =
1 += TDE(backup from smss to azure) =
2 2  
3 3  
4 -This document outlines the process of **encrypting SQL Server databases** using **Transparent Data Encryption (TDE)** and backing them up to **Azure Storage**. TDE ensures data at rest is encrypted, leveraging a **Master Key (MK)**, **TDE Certificate**, and **Database Encryption Key (DEK)** for encryption.
4 +1 Create master key in master database (set master key)
5 5  
6 -The process also includes creating a **credential** for secure backup to **Azure Blob Storage**, providing a scalable and secure solution for storing encrypted databases in the cloud.
6 +2 Create TDE certificate (encrypted by MK)
7 7  
8 +3 Backup the Certificate and private key, By encryption with a password ( did not do it in this case due to storage blog problems)
8 8  
9 -[[image:image-20250305152543-1.png]]
10 +4 Choose DB to create the DEK ,Create database encryption key (DEK) with algorithm ( AES= 256) and encryption by certificate
10 10  
12 +5 Set encryption on for the database
11 11  
12 -**~1. Create a Master Key in the master Database**
13 -The first step is to create a **Master Key** in the master database. This key will be used to encrypt other cryptographic objects, such as certificates and symmetric keys, within SQL Server.
14 +-- 6 Create a new credential with the SAS token
15 +CREATE CREDENTIAL [https://zagpebslab.blob.core.windows.net/sql-backups]
16 +WITH IDENTITY = 'SHARED ACCESS SIGNATURE',
17 +SECRET = 'sp=racwdli&st=2025-02-25T13:28:42Z&se=2026-02-25T21:28:42Z&spr=https&sv=2022-11-02&sr=c&sig=kBFwlj5S5eqBEE32LM1EFebBY0W94uEFiwOXo3R0yt4%3D';
18 +Go--
14 14  
20 +--7 Perform the database backup with the provided parameters
21 +EXECUTE dba.dbo.DatabaseBackup
22 + @Databases = 'dba',                          -- Replace with your database name
23 + @URL = '[[https:~~/~~/zagpebslab.blob.core.windows.net/sql-backups'>>https://zagpebslab.blob.core.windows.net/sql-backups']], -- Azure Blob Storage URL
24 + @BackupType = 'Full',                        -- Full backup
25 + @CopyOnly = 'Y', -- Copy-only backup to avoid breaking backup chain
26 + @Compress = 'Y',                             -- Compress the backup
27 + @Verify = 'N'; -- No verification of backup
28 +GO--
15 15  
16 -**2. Create a TDE Certificate (Encrypted by the Master Key)**
17 -Next, generate a **TDE certificate** that will be used to encrypt the **Database Encryption Key (DEK)**. This certificate is encrypted by the **Master Key** created in step 1, providing an additional layer of security.
18 18  
31 +The backup was unable to be done from smss to azure ( the MI does not support encrypted DBs to be backed up from smss to azure)
19 19  
20 -**3. Choose the Database to Create the Database Encryption Key (DEK)**
21 -For the selected database, create the **Database Encryption Key (DEK)**. The DEK will be encrypted by the **TDE certificate** and will use the **AES-256 encryption algorithm** to ensure data is securely encrypted at rest.
33 +We have unencrypted a database and backed it up from ssms to azure blob successfully
22 22  
23 23  
24 -**4. Enable Encryption for the Database**
25 -Once the **DEK** has been created, enable **TDE** for the database. This ensures that all data written to the database is automatically encrypted at rest, providing full protection for sensitive information.
36 +Conclusion: Can be done with and unencrypted DB but not with an Encrypted one>
26 26  
27 27  
28 -**5. Create a Credential with a SAS Token**
29 -Finally, create a **credential** that allows SQL Server to access Azure Blob Storage. This credential is created using a **Shared Access Signature (SAS) token**, which ensures secure and authenticated access to the storage account for backup purposes.
30 30  
31 -{{code language="sql"}}
32 -drop credential [https://zagpebslab.blob.core.windows.net/sql-backups]
33 -CREATE CREDENTIAL [https://zagpebslab.blob.core.windows.net/sql-backups]
34 -WITH IDENTITY='SHARED ACCESS SIGNATURE'
35 -, SECRET = 'sp=racwdli&st=2025-02-25T13:28:42Z&se=2026-02-25T21:28:42Z&spr=https&sv=2022-11-02&sr=c&sig=kBFwlj5S5eqBEE32LM1EFebBY0W94uEFiwOXo3R0yt4%3D'
36 -GO
37 -
38 -{{/code}}
39 39  
40 40  
41 -**~ 6. Use a Stored Procedure to Back Up to Azure Storage Account**
42 += **Using TDE directly from azure portal** =
42 42  
43 -{{code language="sql"}}
44 -EXECUTE dba.dbo.DatabaseBackup
45 -@Databases = 'dba',
46 -@URL = 'https://zagpebslab.blob.core.windows.net/sql-backups',
47 -@BackupType = 'Full',
48 -@CopyOnly = 'Y',
49 -@Compress = 'Y',
50 -@Verify = 'N'
51 -{{/code}}
52 52  
53 -=== ===
54 54  
55 -=== Conclusion: Backup to Azure Storage Account with TDE Encrypted Databases ===
56 56  
57 -The attempt to back up an **encrypted database** (with Transparent Data Encryption - TDE) from **SQL Server Management Studio (SSMS)** to an Azure Storage Account was unsuccessful. This issue arises because **Azure does not permit TDE-encrypted databases to be backed up directly to Azure Storage using SSMS**.
58 58  
59 -However, after decrypting the database, we were able to successfully back it up to the Azure Storage Account via SSMS. This confirms that **backups can be performed on an unencrypted database**, but **not on an encrypted database**.
60 60  
61 61  
62 62  
63 63  
64 64  
65 -= **2. Enabling Transparent Data Encryption (TDE) Using Azure Key Vault** =
66 66  
67 67  
68 -**Introduction:** This document outlines the process of enabling **Transparent Data Encryption (TDE)** on an **Azure SQL Managed Instance (SQL MI)** using a **Customer-Managed Key (CMK)** stored in **Azure Key Vault**. The encryption is managed using an asymmetric key from **Azure Key Vault**, ensuring that all data within the SQL Managed Instance is encrypted using a strong encryption algorithm.
69 69  
70 70  
71 -===== **1. Generate a Key in Azure Key Vault** =====
72 72  
73 73  
74 -**- Navigate to Azure Key Vault:**
75 75  
76 -* Go to the **Azure Portal** and select **Key Vault** (DemoRudiTest).
77 77  
78 -**- Generate a New Key:**
79 79  
80 -* Go to the **Keys** section and click **Generate** to create a new key.
81 81  
82 -**- Configure Key Settings:**
83 83  
84 -* **Name the Key**: Choose a name for your key, e.g., mysqlmikey.
85 -* **Key Type**: Select **RSA** as the key type.
86 -* **RSA Key Size**: Choose an **RSA key size** of **2048-bit**. (optional)
87 87  
88 - Note:
65 +1 CREATE MASTER KEY ENCRYPTION BY PASSWORD = 'YourStrongPasswordHere!';
66 +GO
89 89  
90 -* switching from 2048-bit RSA to 4096-bit RSA for TDE will affect performance, but the actual impact might be minor, especially on modern hardware and typical workloads.
91 -* **It will likely affect CPU usage** more than disk I/O, and the impact might be more noticeable during key management operations (key generation, encryption, etc.).
92 -* If your database is not under heavy load and your hardware can handle the extra processing, the trade-off for better security may be worth it.
68 +CREATE CERTIFICATE TDE_Certificate
69 +WITH SUBJECT = 'TDE Certificate';
70 +GO
93 93  
94 -**- Create the Key:**
72 +2 USE master;
73 +GO
95 95  
96 -* Click **Create** to generate the key.
75 +SELECT
76 + cert.name AS Certificate_Name,
77 + cert.subject AS Certificate_Subject,
78 + cert.issuer_name AS Issuer_Name,
79 + cert.pvt_key_encryption_type AS Private_Key_Encryption_Type
80 +FROM
81 + sys.certificates cert
82 +WHERE
83 + cert.name LIKE 'TDE%';
97 97  
98 -===== **2. Enable TDE on the SQL Managed Instance** =====
99 99  
100 -===== =====
86 +3 BACKUP CERTIFICATE TDE_Certificate
87 +TO FILE = https://zagpebslab.blob.core.windows.net/sql-backups?sp=racwl&st=2025-02-25T13:28:42Z&se=2026-02-25T21:28:42Z&spr=https&sv=2022-11-02&sr=c&sig=eQKxB%2F0bg5cX71PmhUTlGHLCnIwSbe5CLOWVVkaDR1g%3D\TDE_Certificate.cer'
88 +WITH PRIVATE KEY (
89 + FILE = https://zagpebslab.blob.core.windows.net/sql-backups?sp=racwl&st=2025-02-25T13:28:42Z&se=2026-02-25T21:28:42Z&spr=https&sv=2022-11-02&sr=c&sig=eQKxB%2F0bg5cX71PmhUTlGHLCnIwSbe5CLOWVVkaDR1g%3D\TDE_PrivateKey.pvk',
90 + ENCRYPTION BY PASSWORD = 'AnotherStrongPasswordHere!'
91 +);
92 +GO
101 101  
102 -**- Navigate to Your Managed Instance:**
103 103  
104 -* Go to your **SQL Managed Instance** (sqlmi-ebs-lab).
95 +USE Normal;
96 +GO
105 105  
106 -**- Enable Transparent Data Encryption (TDE):**
98 +-- 6. Create a Database Encryption Key (DEK) and encrypt it with the TDE certificate
99 +CREATE DATABASE ENCRYPTION KEY
100 +WITH ALGORITHM = AES_256
101 +ENCRYPTION BY SERVER CERTIFICATE TDE_Certificate;
102 +GO--
107 107  
108 -* Under **Security**, select **Transparent Data Encryption**.
104 +USE [dba]
105 +GO
109 109  
110 -**- Configure TDE with a Customer-Managed Key (CMK):**
107 +CREATE DATABASE ENCRYPTION KEY
108 +WITH ALGORITHM = AES_256
109 +ENCRYPTION BY SERVER CERTIFICATE TDE_Certificate;
110 +GO
111 111  
112 -* Select **Customer-managed key** as the encryption type.
113 -* Choose the key you created earlier from **Azure Key Vault** (mysqlmikey).
114 114  
115 -**- Set the Key as Default TDE Protector:**
113 +USE [dba1]
114 +GO
116 116  
117 -* Make the key the **default TDE protector** for your instance.
116 +CREATE DATABASE ENCRYPTION KEY
117 +WITH ALGORITHM = AES_256
118 +ENCRYPTION BY SERVER CERTIFICATE TDE_Certificate;
119 +GO
118 118  
119 -**- Save Configuration:**
120 120  
121 -* Click **Save** to apply the changes.
122 +USE [dba2]
123 +GO
122 122  
123 -=== **Conclusion** ===
125 +CREATE DATABASE ENCRYPTION KEY
126 +WITH ALGORITHM = AES_256
127 +ENCRYPTION BY SERVER CERTIFICATE TDE_Certificate;
128 +GO
124 124  
125 -After following these steps, **TDE** has been successfully enabled on your **SQL Managed Instance** using an **asymmetric key** stored in **Azure Key Vault**. All databases within the instance are now encrypted using the same encryption key (identified by the same encryption thumbprint). You can now securely back up these encrypted databases from **SSMS** to **Azure Storage**.
126 126  
127 -This process ensures that your data is protected both at rest and during backup, offering enhanced security for your managed databases in the cloud.
131 +USE [dba3]
132 +GO
128 128  
134 +CREATE DATABASE ENCRYPTION KEY
135 +WITH ALGORITHM = AES_256
136 +ENCRYPTION BY SERVER CERTIFICATE TDE_Certificate;
137 +GO
129 129  
139 +USE [xwiki]
140 +GO
130 130  
131 -=== **1. Backup Specific Databases Using SQL Server Agent Jobs** ===
142 +CREATE DATABASE ENCRYPTION KEY
143 +WITH ALGORITHM = AES_256
144 +ENCRYPTION BY SERVER CERTIFICATE TDE_Certificate;
145 +GO
132 132  
133 -This document describes the process of creating an automated **SQL Server Agent Job** to back up only the **DBA databases** in a SQL Server instance. The backups will occur **daily at 3:00 AM** and will be stored in an **Azure Storage Account** for secure and reliable cloud storage.
134 134  
135 -----
148 +-- 7. Enable Transparent Data Encryption (TDE) on the database
149 +ALTER DATABASE dba
150 +SET ENCRYPTION ON;
151 +GO--
136 136  
137 -==== **1. Create the Backup Script** ====
138 138  
154 +select name, database_id, state_desc
155 +from sys.databases
139 139  
140 -====== **- Declaring Variables** ======
141 141  
142 -{{code language="sql"}}
143 -DECLARE @DatabaseName NVARCHAR(128)
144 -DECLARE @BackupContainerURL NVARCHAR(512)
145 -{{/code}}
158 +SELECT
159 + database_id,
160 + key_algorithm,
161 + key_length,
162 + encryption_state_desc
163 + encryptor_type
146 146  
147 -DECLARE @DatabaseName NVARCHAR(128) DECLARE @BackupContainerURL NVARCHAR(512)
165 +FROM
166 + sys.dm_database_encryption_keys;
148 148  
149 -* **@DatabaseName**: A variable to hold the name of the database during each iteration of the loop.
150 -* **@BackupContainerURL**: A variable to store the URL of the Azure Blob Storage container where the database backups will be stored.
151 151  
152 -----
169 + Select * from sys.dm_database_encryption_keys
153 153  
154 -====== **2. Setting the Azure Blob Storage URL** ======
155 155  
156 -{{code language="sql"}}
157 -SET @BackupContainerURL = 'https://<your_storage_account>.blob.core.windows.net/sql-backups/'
158 -{{/code}}
172 + BACKUP DATABASE [dba2]
173 +TO URL = '[[https:~~/~~/zagpebslab.blob.core.windows.net/sql-backups?sp=racwl&st=2025-02-25T13:28:42Z&se=2026-02-25T21:28:42Z&spr=https&sv=2022-11-02&sr=c&sig=eQKxB%2F0bg5cX71PmhUTlGHLCnIwSbe5CLOWVVkaDR1g%3D'>>https://zagpebslab.blob.core.windows.net/sql-backups?sp=racwl&st=2025-02-25T13:28:42Z&se=2026-02-25T21:28:42Z&spr=https&sv=2022-11-02&sr=c&sig=eQKxB%2F0bg5cX71PmhUTlGHLCnIwSbe5CLOWVVkaDR1g%3D']]
174 +With copy_only
175 +GO
159 159  
160 160  
161 -----
178 +BACKUP DATABASE [dba2]
179 +TO URL = '[[https:~~/~~/zagpebslab.blob.core.windows.net/sql-backups?sp=racwl&st=2025-02-25T13:28:42Z&se=2026-02-25T21:28:42Z&spr=https&sv=2022-11-02&sr=c&sig=eQKxB%2F0bg5cX71PmhUTlGHLCnIwSbe5CLOWVVkaDR1g%3D'>>https://zagpebslab.blob.core.windows.net/sql-backups?sp=racwl&st=2025-02-25T13:28:42Z&se=2026-02-25T21:28:42Z&spr=https&sv=2022-11-02&sr=c&sig=eQKxB%2F0bg5cX71PmhUTlGHLCnIwSbe5CLOWVVkaDR1g%3D']],
180 +
181 + COPY_ONLY, -- Ensures the backup does not affect the regular backup chain
182 + COMPRESSION,  -- Optional: Compresses the backup to save storage space
183 + STATS = 10 -- Optional: Provides backup progress status
184 +GO--
162 162  
163 -====== **3. Declaring the Cursor** ======
164 164  
165 165  
166 -{{code language="sql"}}
167 -DECLARE db_cursor CURSOR FOR
168 -SELECT name
169 -FROM sys.databases
170 -WHERE name LIKE 'dba%' -- Only pick databases that start with 'dba'
171 -{{/code}}
188 +-- Step 1: Drop the existing credential (if needed)
189 +DROP CREDENTIAL [https://zagpebslab.blob.core.windows.net/sql-backups];
190 +GO--
172 172  
173 -* **Cursor Declaration**:
174 -** The cursor db_cursor is declared to loop through the list of databases in the sys.databases system view.
175 -** The **WHERE name LIKE 'dba%'** clause ensures that only databases with names starting with dba will be processed. For example, databases like dbaTest, dbaProd, etc., will be included in the loop.
176 -** **sys.databases**: A system catalog view that contains information about each database in the SQL Server instance.
192 +-- Step 2: Create a new credential with the SAS token
193 +CREATE CREDENTIAL [https://zagpebslab.blob.core.windows.net/sql-backups]
194 +WITH IDENTITY = 'SHARED ACCESS SIGNATURE',
195 +SECRET = 'sp=racwdli&st=2025-02-25T13:28:42Z&se=2026-02-25T21:28:42Z&spr=https&sv=2022-11-02&sr=c&sig=kBFwlj5S5eqBEE32LM1EFebBY0W94uEFiwOXo3R0yt4%3D';
196 +GO--
177 177  
178 -----
198 +-- Step 3: Perform the database backup with the provided parameters
199 +EXECUTE dba.dbo.DatabaseBackup
200 + @Databases = 'dba',                          -- Replace with your database name
201 + @URL = '[[https:~~/~~/zagpebslab.blob.core.windows.net/sql-backups'>>https://zagpebslab.blob.core.windows.net/sql-backups']], -- Azure Blob Storage URL
202 + @BackupType = 'Full',                        -- Full backup
203 + @CopyOnly = 'Y', -- Copy-only backup to avoid breaking backup chain
204 + @Compress = 'Y',                             -- Compress the backup
205 + @Verify = 'N'; -- No verification of backup
206 +GO--
179 179  
180 -====== **4. Opening the Cursor** ======
181 181  
182 -{{code language="sql"}}
183 -OPEN db_cursor
184 -FETCH NEXT FROM db_cursor INTO @DatabaseName
185 -{{/code}}
186 186  
187 -OPEN db_cursor FETCH NEXT FROM db_cursor INTO @DatabaseName
188 188  
189 -* **OPEN db_cursor**: This opens the cursor for reading the results.
190 -* **FETCH NEXT**: The FETCH NEXT statement retrieves the first database name that meets the LIKE 'dba%' condition and stores it in the @DatabaseName variable. This will be used in the next step where the backup procedure is executed.
191 191  
192 -----
212 +select name, database_id, state_desc
213 +from sys.databases
193 193  
194 -====== **5. Looping Through Databases** ======
195 195  
196 -{{code language="sql"}}
197 --- Loop through each database and execute the stored procedure
198 -WHILE @@FETCH_STATUS = 0
199 -BEGIN
200 - -- Print current database for logging/debugging
201 - PRINT 'Backing up database: ' + @DatabaseName
216 +SELECT
217 + database_id,
218 + key_algorithm,
219 + key_length,
220 + encryption_state_desc
221 + encryptor_type
202 202  
203 - -- Execute the DatabaseBackup stored procedure for each database
204 - EXECUTE dba.dbo.DatabaseBackup
205 - @Databases = @DatabaseName, -- Specify the current database
206 - @URL = @BackupContainerURL, -- Azure Blob Storage URL
207 - @BackupType = 'Full', -- Full backup type
208 - @CopyOnly = 'Y', -- Use copy-only backup (this doesn’t affect the transaction log chain)
209 - @Compress = 'Y', -- Enable compression
210 - @Verify = 'N'; -- Skip verification after backup
223 +FROM
224 + select * from sys.dm_database_encryption_keys;
211 211  
212 -{{/code}}
213 213  
227 + select name, is_encrypted from sys.databases
214 214  
215 -* **WHILE @@FETCH_STATUS = 0**: The loop will continue as long as the FETCH command successfully retrieves a database name. @@FETCH_STATUS is a system function that returns 0 if the fetch operation is successful.
216 -* **PRINT**: This line prints the name of the database that is currently being backed up. It helps with logging or debugging purposes, as you can track which database is being processed at any given time.
217 -* (((
218 -**EXECUTE dba.dbo.DatabaseBackup**:
219 219  
220 -* This calls a stored procedure named dba.dbo.DatabaseBackup for each database.
221 -* The parameters passed to the stored procedure:
222 -** **@Databases = @DatabaseName**: Specifies which database to back up (the current database being processed).
223 -** **@URL = @BackupContainerURL**: Specifies the destination Azure Blob Storage URL.
224 -** **@BackupType = 'Full'**: Specifies the backup type, which is a **Full** backup (this means all data in the database is backed up).
225 -** **@CopyOnly = 'Y'**: Specifies that this is a **copy-only backup**. This ensures that the backup does not affect the transaction log chain and does not interfere with regular backups.
226 -** **@Compress = 'Y'**: Enables compression of the backup, reducing the size of the backup file.
227 -** **@Verify = 'N'**: Specifies that the backup verification step should be skipped. (Verification can be added if needed for additional safety.)
228 -)))
230 + SELECT
231 + cert.name AS Certificate_Name,
232 + cert.subject AS Certificate_Subject,
233 + cert.issuer_name AS Issuer_Name,
234 + cert.pvt_key_encryption_type AS Private_Key_Encryption_Type
235 +FROM
236 + sys.certificates cert
237 +WHERE
238 + cert.name LIKE 'TDE%';
229 229  
230 -----
240 + ALTER DATABASE dba1
241 +SET ENCRYPTION off;
242 +GO
231 231  
232 -====== **6. Fetch the Next Database** ======
233 233  
234 -{{code language="sql"}}
235 - -- Fetch the next database in the cursor
236 - FETCH NEXT FROM db_cursor INTO @DatabaseName
245 +Use dba1;
246 +DROP DATABASE ENCRYPTION KEY;
237 237  
238 -{{/code}}
239 239  
240 -~-~- Fetch the next database in the cursor FETCH NEXT FROM db_cursor INTO @DatabaseName
249 +USE [dba1]
250 +GO
241 241  
242 -* **FETCH NEXT**: After executing the backup for the current database, this statement retrieves the next database from the cursor and stores it in the @DatabaseName variable. The loop will continue until all matching databases have been processed.
252 +CREATE DATABASE ENCRYPTION KEY
253 +WITH ALGORITHM = AES_256
254 +ENCRYPTION BY SERVER CERTIFICATE TDE_Certificate;
255 +GO
243 243  
244 -----
245 245  
246 -====== **7. Closing and Deallocating the Cursor** ======
247 247  
248 -{{code language="sql"}}
249 --- Close and deallocate the cursor to clean up resources
250 -CLOSE db_cursor
251 -DEALLOCATE db_cursor
252 -
259 +ALTER DATABASE dba1
260 +SET ENCRYPTION ON
253 253  
254 -{{/code}}
255 255  
256 -* **CLOSE db_cursor**: This closes the cursor once the loop finishes processing all databases.
257 -* **DEALLOCATE db_cursor**: This deallocates the cursor, freeing up any resources used by the cursor. It’s a good practice to always deallocate cursors to avoid resource leaks.
258 258  
259 -====== ======
260 260  
261 -====== **8. Full Script** ======
262 262  
263 263  
264 -{{code language="sql"}}
265 -DECLARE @DatabaseName NVARCHAR(128)
266 -DECLARE @BackupContainerURL NVARCHAR(512)
267 267  
268 -SET @BackupContainerURL = 'https://zagpebslab.blob.core.windows.net/sql-backups'
269 269  
270 -DECLARE db_cursor CURSOR FOR
271 -SELECT name
272 -FROM sys.databases
273 -WHERE name LIKE 'dba%'
274 274  
275 -OPEN db_cursor
276 -FETCH NEXT FROM db_cursor INTO @DatabaseName
277 277  
278 -WHILE @@FETCH_STATUS = 0
279 -BEGIN
280 280  
281 -PRINT 'Backing up database: ' + @DatabaseName
282 282  
283 -EXECUTE dba.dbo.DatabaseBackup
284 - @Databases = @DatabaseName,
285 - @URL = @BackupContainerURL,
286 - @BackupType = 'Full',
287 - @CopyOnly = 'Y',
288 - @Compress = 'Y',
289 - @Verify = 'N';
290 290  
291 -FETCH NEXT FROM db_cursor INTO @DatabaseName
292 -END
293 293  
294 -CLOSE db_cursor
295 -DEALLOCATE db_cursor
296 296  
297 -{{/code}}
298 298  
299 299  
300 300  
301 301  
302 -=== ===
303 303  
304 304  
305 305  
... ... @@ -314,4 +314,40 @@
314 314  
315 315  
316 316  
294 +{{code language="sql"}}
295 +USE master;
296 +GO
297 +CREATE MASTER KEY ENCRYPTION BY PASSWORD = '******';
298 +GO
299 +
300 +CREATE CERTIFICATE EBSphere_TDE_SQL2019_Cert WITH SUBJECT = 'Database_Encryption';
301 +GO
302 +
303 +BACKUP CERTIFICATE EBSphere_TDE_SQL2019_Cert TO FILE = 'D:\temp\EBSphere_TDE_SQL2019_Cert'
304 +WITH PRIVATE KEY (file = 'D:\temp\EBSphere_TDE_SQL2019_Cert_Key.pvk',
305 +ENCRYPTION BY PASSWORD='*****')
306 +
307 +USE Everest_TDE_Master;
308 +GO
309 +CREATE DATABASE ENCRYPTION KEY
310 +WITH ALGORITHM = AES_256
311 +ENCRYPTION BY SERVER CERTIFICATE EBSphere_TDE_SQL2019_Cert;
312 +GO
313 +ALTER DATABASE Everest_TDE_Master
314 +SET ENCRYPTION ON;
315 +GO
316 +
317 +USE Everest_TDE_Master_Documents;
318 +GO
319 +CREATE DATABASE ENCRYPTION KEY
320 +WITH ALGORITHM = AES_256
321 +ENCRYPTION BY SERVER CERTIFICATE EBSphere_TDE_SQL2019_Cert;
322 +GO
323 +ALTER DATABASE Everest_TDE_Master_Documents
324 +SET ENCRYPTION ON;
325 +GO
326 +{{/code}}
327 +
328 +
329 +
317 317  
image-20250305152543-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.rudim
Size
... ... @@ -1,1 +1,0 @@
1 -19.6 KB
Content

Applications

Navigation

Need help?

If you need help with XWiki you can contact: