Lokasi ngalangkungan proxy:   [ UP ]  
[Ngawartoskeun bug]   [Panyetelan cookie]                
Skip to content

Commit 4cb0452

Browse files
authored
Update troubleshoot-tde.md
1 parent b61f896 commit 4cb0452

1 file changed

Lines changed: 6 additions & 6 deletions

File tree

docs/relational-databases/security/encryption/troubleshoot-tde.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ ms.prod: sql
1212
ms.technology: security
1313
ms.reviewer: vanto
1414
ms.topic: conceptual
15-
ms.date: 11/06/2019
15+
ms.date: 03/04/2022
1616
monikerRange: "= azuresqldb-current || = azure-sqldw-latest"
1717
---
1818
# Common errors for transparent data encryption with customer-managed keys in Azure Key Vault
@@ -177,7 +177,7 @@ EventName: MakeManagedDbInaccessible
177177

178178
Status: Started
179179

180-
Description: Database <name> on managed server <name> has lost access to Azure Key Vault Key and is now transitioning to inaccessible state.
180+
Description: Database on managed server has lost access to Azure Key Vault Key and is now transitioning to inaccessible state.
181181

182182

183183
**Event when the database has automatically come back online**
@@ -196,7 +196,7 @@ EventName: MakeManagedDbAccessible
196196

197197
Status: Succeeded
198198

199-
Description: Access to Azure Key Vault Key has been re-established and all managed databases in server <name> is now online.
199+
Description: Access to Azure Key Vault Key has been re-established and all managed databases in server is now online.
200200

201201

202202
**Event when the issue wasn’t resolved within 30 minutes and Azure Key Vault key access has to be validated manually**
@@ -215,7 +215,7 @@ EventName: MakeManagedDbInaccessible
215215

216216
Status: Succeeded
217217

218-
Description: Database <name> on managed server <name> is inaccessible and requires user to re-establish access to Azure Key Vault Key.
218+
Description: Database on managed server is inaccessible and requires user to re-establish access to Azure Key Vault Key.
219219

220220

221221
**Event when db comes online after manual key re-validation**
@@ -234,7 +234,7 @@ EventName: MakeManagedDbAccessible
234234

235235
Status: Succeeded
236236

237-
Description: Access to Azure Key Vault Key has been re-established and all managed databases in server <name> is now online.
237+
Description: Access to Azure Key Vault Key has been re-established and all managed databases in server is now online.
238238

239239

240240
**Event when re-validation of Azure Key Vault key access has succeeded and the db is coming back online**
@@ -253,7 +253,7 @@ EventName: MakeManagedDbAccessible
253253

254254
Status: Started
255255

256-
Description: Access to Azure Key Vault Key has been re-established, operation to make all databases accessible in managed server <name> started
256+
Description: Access to Azure Key Vault Key has been re-established, operation to make all databases accessible in managed server started
257257

258258

259259
**Event when re-validation of Azure Key Vault key access has failed**

0 commit comments

Comments
 (0)