Skip to content

Commit 2fa7074

Browse files
20230908 edit pass
1 parent 4125290 commit 2fa7074

2 files changed

Lines changed: 5 additions & 3 deletions

File tree

azure-sql/database/troubleshoot-transaction-log-errors-issues.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ description: Provides steps to troubleshoot transaction log issues in Azure SQL
55
author: WilliamDAssafMSFT
66
ms.author: wiassaf
77
ms.reviewer: wiassaf, mathoma
8-
ms.date: 08/30/2023
8+
ms.date: 09/08/2023
99
ms.service: sql-database
1010
ms.subservice: development
1111
ms.topic: troubleshooting

azure-sql/managed-instance/troubleshoot-transaction-log-errors-issues.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ description: Provides steps to troubleshoot transaction log issues in Azure SQL
55
author: WilliamDAssafMSFT
66
ms.author: wiassaf
77
ms.reviewer: wiassaf, mathoma
8-
ms.date: 08/30/2023
8+
ms.date: 09/08/2023
99
ms.service: sql-managed-instance
1010
ms.subservice: development
1111
ms.topic: troubleshooting
@@ -117,7 +117,9 @@ If the transaction log is prevented from truncating in Azure SQL Managed Instanc
117117

118118
`40552: The session has been terminated because of excessive transaction log space usage. Try modifying fewer rows in a single transaction.`
119119

120-
To resolve this issue, try the following methods:
120+
While Error 9002 is more common than Error 40552 in Azure SQL Managed Instance, both can occur.
121+
122+
To resolve Error 40552, try the following methods:
121123

122124
1. The issue can occur in any DML operation such as insert, update, or delete. Review the transaction to avoid unnecessary writes. Try to reduce the number of rows that are operated on immediately by implementing batching or splitting into multiple smaller transactions. For more information, see [How to use batching to improve application performance](../performance-improve-use-batching.md?view=azuresql-mi&preserve-view=true).
123125
1. The issue can occur because of index rebuild operations. To avoid this issue, ensure the following formula is true: (number of rows that are affected in the table) multiplied by (the average size of field that's updated in bytes + 80) < 2 gigabytes (GB). For large tables, consider creating partitions and performing index maintenance only on some partitions of the table. For more information, see [Create Partitioned Tables and Indexes](/sql/relational-databases/partitions/create-partitioned-tables-and-indexes?view=azuresqldb-current&preserve-view=true).

0 commit comments

Comments
 (0)