Skip to content

Commit 5cda8a9

Browse files
Merge pull request #36129 from MicrosoftDocs/main
Auto Publish – main to live - 2025-12-19 23:30 UTC
2 parents e555cd8 + d8ecc24 commit 5cda8a9

2 files changed

Lines changed: 11 additions & 8 deletions

File tree

azure-sql/database/auditing-overview.md

Lines changed: 11 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -2,10 +2,10 @@
22
title: Auditing
33
titleSuffix: Azure SQL Database and Azure Synapse Analytics
44
description: SQL Auditing for Azure SQL Database and Azure Synapse Analytics tracks database events and writes them to an audit log in your Azure storage account, Log Analytics workspace, or Event Hubs.
5-
author: sravanisaluru
6-
ms.author: srsaluru
7-
ms.reviewer: wiassaf, vanto, mathoma
8-
ms.date: 09/04/2025
5+
author: WilliamDAssafMSFT
6+
ms.author: wiassaf
7+
ms.reviewer: srsaluru, vanto, mathoma
8+
ms.date: 12/19/2025
99
ms.service: azure-sql-database
1010
ms.subservice: security
1111
ms.topic: conceptual
@@ -54,6 +54,13 @@ You can use SQL Database auditing to:
5454
- Permissions required to view Audit logs:
5555
- `VIEW DATABASE SECURITY AUDIT` permission in user database
5656

57+
### Recommended auditing approach for large OLTP workloads
58+
59+
For environments with many databases running heavy OLTP workloads, using server‑level auditing with default settings can lead to very large audit volumes across the logical server. Since all events from all databases are written into the same audit folder, querying audit logs for a single database becomes slow and operationally expensive. To improve performance and reduce noise:
60+
61+
- **Switch to database‑level auditing**. Each database writes to its own audit log folder, reducing the total volume scanned and making retrieval faster.
62+
- **Review the audit configuration**. Determine whether capturing all batch‑completed events is necessary, or if a custom filtered configuration can meet your security and compliance requirements.
63+
5764
## Auditing limitations
5865

5966
- Enabling auditing on a paused **Azure Synapse SQL pool** isn't supported. To enable auditing, resume the **Synapse SQL pool**.

docs/sql-server/azure-arc/faq.yml

Lines changed: 0 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -130,10 +130,6 @@ sections:
130130
- Subscribe to Activity Log events for when usage records are not received when expected or when recurring billing starts or is happening.
131131
Review [Manage recurrent billing for pay-as-you go licenses](manage-pay-as-you-go-transition.md) for details.
132132
133-
- question: Can I enable recurring pay-as-you-go billing for my Arc-enabled SQL Servers that use the license with SA to ensure continuous reclassification?
134-
answer: |
135-
No. Recurring billing is a feature of pay-as-you-go subscriptions.
136-
137133
additionalContent: |
138134
139135
## Related content

0 commit comments

Comments
 (0)