Changes for page sql-tde

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

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

Summary

Details

Page properties
Content
... ... @@ -6,9 +6,6 @@
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 -
12 12  **~1. Create a Master Key in the master Database**
13 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 14  
... ... @@ -50,7 +50,7 @@
50 50  @Verify = 'N'
51 51  {{/code}}
52 52  
53 -=== ===
50 +=== ===
54 54  
55 55  === Conclusion: Backup to Azure Storage Account with TDE Encrypted Databases ===
56 56  
... ... @@ -75,10 +75,12 @@
75 75  
76 76  * Go to the **Azure Portal** and select **Key Vault** (DemoRudiTest).
77 77  
75 +
78 78  **- Generate a New Key:**
79 79  
80 80  * Go to the **Keys** section and click **Generate** to create a new key.
81 81  
80 +
82 82  **- Configure Key Settings:**
83 83  
84 84  * **Name the Key**: Choose a name for your key, e.g., mysqlmikey.
... ... @@ -91,36 +91,46 @@
91 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 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.
93 93  
93 +
94 94  **- Create the Key:**
95 95  
96 96  * Click **Create** to generate the key.
97 97  
98 98  
99 +
100 +
99 99  ===== **2. Enable TDE on the SQL Managed Instance** =====
100 100  
101 -===== =====
103 +===== =====
102 102  
103 103  **- Navigate to Your Managed Instance:**
104 104  
105 105  * Go to your **SQL Managed Instance** (sqlmi-ebs-lab).
106 106  
109 +
107 107  **- Enable Transparent Data Encryption (TDE):**
108 108  
109 109  * Under **Security**, select **Transparent Data Encryption**.
110 110  
114 +
111 111  **- Configure TDE with a Customer-Managed Key (CMK):**
112 112  
113 113  * Select **Customer-managed key** as the encryption type.
114 114  * Choose the key you created earlier from **Azure Key Vault** (mysqlmikey).
115 115  
120 +
121 +
116 116  **- Set the Key as Default TDE Protector:**
117 117  
118 118  * Make the key the **default TDE protector** for your instance.
119 119  
126 +
120 120  **- Save Configuration:**
121 121  
122 122  * Click **Save** to apply the changes.
123 123  
131 +
132 +
124 124  === **Conclusion** ===
125 125  
126 126  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**.
... ... @@ -257,6 +257,7 @@
257 257  * **CLOSE db_cursor**: This closes the cursor once the loop finishes processing all databases.
258 258  * **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.
259 259  
269 +(% class="wikigeneratedid" %)
260 260  ====== ======
261 261  
262 262  ====== **8. Full Script** ======
... ... @@ -361,6 +361,7 @@
361 361  
362 362  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.
363 363  
374 +(% class="wikigeneratedid" %)
364 364  === ===
365 365  
366 366  ===== Note: We could use the job activity monitor to see if the job executed successfully. =====
... ... @@ -672,3 +672,5 @@
672 672  {{/code}}
673 673  
674 674  
686 +
687 +
image-20250305152543-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.rudim
Size
... ... @@ -1,1 +1,0 @@
1 -19.6 KB
Content

Need help?

If you need help with XWiki you can contact: