Changes for page sql-tde

Last modified by Nikhil Singh on 2026/07/03 08:32

<
From version < 9.1 >
edited by Nikhil Singh
on 2025/02/28 13:57
To version < 10.2 >
edited by Nikhil Singh
on 2025/05/21 12:45
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -6,6 +6,9 @@
6 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.
7 7  
8 8  
9 +[[image:image-20250305152543-1.png]]
10 +
11 +
9 9  **~1. Create a Master Key in the master Database**
10 10  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.
11 11  
... ... @@ -47,7 +47,7 @@
47 47  @Verify = 'N'
48 48  {{/code}}
49 49  
50 -=== ===
53 +=== ===
51 51  
52 52  === Conclusion: Backup to Azure Storage Account with TDE Encrypted Databases ===
53 53  
... ... @@ -72,12 +72,10 @@
72 72  
73 73  * Go to the **Azure Portal** and select **Key Vault** (DemoRudiTest).
74 74  
75 -
76 76  **- Generate a New Key:**
77 77  
78 78  * Go to the **Keys** section and click **Generate** to create a new key.
79 79  
80 -
81 81  **- Configure Key Settings:**
82 82  
83 83  * **Name the Key**: Choose a name for your key, e.g., mysqlmikey.
... ... @@ -90,46 +90,36 @@
90 90  * **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.).
91 91  * 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.
92 92  
93 -
94 94  **- Create the Key:**
95 95  
96 96  * Click **Create** to generate the key.
97 97  
98 98  
99 -
100 -
101 101  ===== **2. Enable TDE on the SQL Managed Instance** =====
102 102  
103 -===== =====
101 +===== =====
104 104  
105 105  **- Navigate to Your Managed Instance:**
106 106  
107 107  * Go to your **SQL Managed Instance** (sqlmi-ebs-lab).
108 108  
109 -
110 110  **- Enable Transparent Data Encryption (TDE):**
111 111  
112 112  * Under **Security**, select **Transparent Data Encryption**.
113 113  
114 -
115 115  **- Configure TDE with a Customer-Managed Key (CMK):**
116 116  
117 117  * Select **Customer-managed key** as the encryption type.
118 118  * Choose the key you created earlier from **Azure Key Vault** (mysqlmikey).
119 119  
120 -
121 -
122 122  **- Set the Key as Default TDE Protector:**
123 123  
124 124  * Make the key the **default TDE protector** for your instance.
125 125  
126 -
127 127  **- Save Configuration:**
128 128  
129 129  * Click **Save** to apply the changes.
130 130  
131 -
132 -
133 133  === **Conclusion** ===
134 134  
135 135  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**.
... ... @@ -266,7 +266,6 @@
266 266  * **CLOSE db_cursor**: This closes the cursor once the loop finishes processing all databases.
267 267  * **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.
268 268  
269 -(% class="wikigeneratedid" %)
270 270  ====== ======
271 271  
272 272  ====== **8. Full Script** ======
... ... @@ -371,7 +371,6 @@
371 371  
372 372  The SQL Server Agent job is now configured to automatically back up the **DBA databases** daily to an **Azure Storage Account**. The job will only back up databases that start with 'dba', and it handles encrypted databases with **Transparent Data Encryption (TDE)**. This ensures secure, encrypted backups are stored in the cloud without requiring manual intervention.
373 373  
374 -(% class="wikigeneratedid" %)
375 375  === ===
376 376  
377 377  ===== Note: We could use the job activity monitor to see if the job executed successfully. =====
... ... @@ -683,5 +683,3 @@
683 683  {{/code}}
684 684  
685 685  
686 -
687 -
image-20250305152543-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.rudim
Size
... ... @@ -1,0 +1,1 @@
1 +19.6 KB
Content

Need help?

If you need help with XWiki you can contact: