Merge pull request #34601 from MicrosoftDocs/main

Merged by Learn.Build PR Management system

Author: learn-build-service-prod[bot]

azure-sql/database/auditing-overview.md

@@ -5,7 +5,7 @@ description: SQL Auditing for Azure SQL Database and Azure Synapse Analytics tra
 author: sravanisaluru
 ms.author: srsaluru
 ms.reviewer: wiassaf, vanto, mathoma
-ms.date: 03/12/2025
+ms.date: 07/02/2025
 ms.service: azure-sql-database
 ms.subservice: security
 ms.topic: conceptual
@@ -39,21 +39,21 @@ You can use SQL Database auditing to:
 > [!IMPORTANT]  
 > Auditing for Azure SQL Database, Azure Synapse Analytics SQL pools, and Azure SQL Managed Instance is optimized for availability and performance of the database or instance being audited. During periods of very high activity or high network load, the auditing feature might allow transactions to proceed without recording all of the events marked for auditing.
 
-## Enhancements to performance, availability, and reliability in server auditing for Azure SQL Database (March 2025)
+## Enhancements to performance, availability, and reliability in server auditing for Azure SQL Database (July 2025 GA)
 
-- Re-architected major portions of SQL Auditing resulting in increased availability and reliability of server audits. As an added benefit, there's closer feature alignment with SQL Server and Azure SQL Managed Instance. Database auditing remains unchanged. 
+- Re-architected major portions of SQL Auditing resulting in increased availability and reliability of server audits. As an added benefit, there's closer feature alignment with SQL Server and Azure SQL Managed Instance. Database auditing remains unchanged.
 - The previous design of auditing triggers a database level audit and executes one audit session for each database in the server. The new architecture of auditing creates one extended event session at the server level that captures audit events for all databases.
 - The new auditing design optimizes memory and CPU, and is consistent with how auditing works in SQL Server and Azure SQL Managed Instance.
 
-### Changes from the re-architecture of server auditing 
+### Changes from the re-architecture of server auditing
 
 - Folder structure change for storage account:
   - One of the primary changes involves a folder structure change for audit logs stored in storage account containers. Previously, server audit logs were written to separate folders; one for each database, with the database name serving as the folder name. With the new update, all server audit logs will be consolidated into a single folder labeled `master`. This behavior is the same as Azure SQL Managed Instance and SQL Server.
 - Folder structure change for read-only replicas:
   - Read-only database replicas previously had their logs stored in a read-only folder. Those logs will now be written into the `master` folder. You can retrieve these logs by filtering on the new column `is_secondary_replica_true`.
 - Permissions required to view Audit logs:
   - Only **Server admin** principals can view audit logs stored in the `master` folder.
-    
+
 ## Auditing limitations
 
 - Enabling auditing on a paused **Azure Synapse SQL pool** isn't supported. To enable auditing, resume the **Synapse SQL pool**.
@@ -84,5 +84,4 @@ You can use SQL Database auditing to:
 - [What's New in Azure SQL Auditing](/shows/data-exposed/server-audit-redesign-for-azure-sql-database-data-exposed)
 - [Get started with Azure SQL Managed Instance auditing](../managed-instance/auditing-configure.md)
 - [Auditing for SQL Server](/sql/relational-databases/security/auditing/sql-server-audit-database-engine)
-
 - [Set up Auditing for Azure SQL Database and Azure Synapse Analytics](auditing-setup.md)

azure-sql/database/doc-changes-updates-release-notes-whats-new.md

@@ -66,6 +66,7 @@ The following table lists features of Azure SQL Database that have been made gen
 
 | Feature | GA Month | Details |
 | --- | --- | --- |
+| **Audit re-architecture** | July 2025 | Increased availability and reliability of server audits through a re-architecture of auditing in Azure SQL Database that is closely aligned with SQL Server and Azure SQL Managed Instance. For more information, see [Auditing](auditing-overview.md#enhancements-to-performance-availability-and-reliability-in-server-auditing-for-azure-sql-database-july-2025-ga).|
 | **Hyperscale increased log generation rate** | May 2025 | The transaction log generation rate in Azure SQL Database Hyperscale single databases has been increased from 100 MiB/s to 150 MiB/s for premium-series and premium-series memory optimized hardware. For more information, read [Blog: Enhancements to Azure SQL Database Hyperscale](https://aka.ms/HSenhancements).|
 | **Hyperscale continuous priming** | May 2025 | [Continuous priming](service-tier-hyperscale.md#continuous-priming) optimizes Hyperscale performance during failovers by priming high availability secondary compute replicas. Continuous priming is now generally available. For more information, read [Blog: Enhancements to Azure SQL Database Hyperscale](https://aka.ms/HSenhancements). |
 | **JSON native data type** | May 2025 | The [**json** data type and JSON aggregate functions](/sql/t-sql/data-types/json-data-type?view=azuresqldb-current&preserve-view=true) provide new capabilities for handling semistructured data in Azure SQL Database. |
@@ -102,6 +103,7 @@ Learn about significant changes to the Azure SQL Database documentation. For pre
 | Changes | Details |
 | --- | --- |
 | **Convert to Hyperscale with geo-replicas (preview)** |The ability to [convert a geo-replicated database non-Hyperscale database to Hyperscale](convert-to-hyperscale.md) using T-SQL, REST API, PowerShell, or Azure CLI is currently a preview feature. For more information, see [Blog: Hyperscale conversion support for geo-replicas](https://aka.ms/hs-conversion-geodr-preview). |
+| **Audit re-architecture GA** | Enhancements to performance, availability, and reliability in server auditing for Azure SQL Database. For more information, see [Auditing](auditing-overview.md#enhancements-to-performance-availability-and-reliability-in-server-auditing-for-azure-sql-database-july-2025-ga). |
 
 ### June 2025
 

azure-sql/managed-instance/automated-backups-overview.md

@@ -2,10 +2,10 @@
 title: Automatic, Geo-Redundant Backups
 titleSuffix: Azure SQL Managed Instance
 description: Learn how Azure SQL Managed Instance automatically backs up all databases and provides point-in-time restore capability.
-author: Stralle
-ms.author: strrodic
-ms.reviewer: mathoma, wiassaf, danil, randolphwest
-ms.date: 05/27/2025
+author: dinethi
+ms.author: dinethi
+ms.reviewer: mathoma, wiassaf, mlandzic, strrodic, danil, randolphwest
+ms.date: 06/26/2025
 ms.service: azure-sql-managed-instance
 ms.subservice: backup-restore
 ms.topic: conceptual
@@ -288,6 +288,17 @@ Microsoft is fully responsible for keeping and rotating keys for databases with
 
 Automatic backups stored in Azure-managed storage accounts are automatically encrypted by Azure storage. Learn more about [Azure Storage encryption for data at rest](/azure/storage/common/storage-service-encryption).
 
+## Common issues with automated backups due to customer actions
+
+While Azure SQL Managed Instance provides automated backups to ensure data protection and recovery, certain customer-side configurations or actions can lead to backup failures. Common scenarios include:
+
+- Insufficient storage for the SQL managed instance. If the storage allocated to your instance is full, automated backups aren't taken.
+- User-defined jobs or scripts that kill system processes can stop automated backup operations.
+- Incorrect DNS settings can prevent the SQL managed instance from accessing required Azure endpoints, including those used for backups, leading to backup failures.
+- The transaction log could fill due to prevented truncation from misconfigured replication, CDC or full storage (at the instance level). If the transaction log is full and can't be truncated, full and differential backups fail, but log backups still succeed without truncating the log file.
+
+To ensure reliable backups, it's important to monitor system resources, validate configuration settings, and avoid interfering with built-in service operations. Make sure to monitor allocated storage, have correct DNS settings, and review custom jobs and replication configurations.
+
 ## Backup integrity
 
 All database backups are taken with the CHECKSUM option to provide additional backup integrity. Automatic testing of automated database backups by the Azure SQL engineering team isn't currently available for Azure SQL Managed Instance. Schedule test backup restoration and DBCC CHECKDB on your databases in SQL Managed Instance around your workload.

docs/relational-databases/polybase/polybase-guide.md

@@ -53,8 +53,9 @@ PolyBase provides these same functionalities for the following SQL products from
 
 | New to [!INCLUDE [sssql25-md](../../includes/sssql25-md.md)] | Details |
 | --- | --- |
-| Native support for CSV, Parquet, & Delta <sup>1</sup> | You don't have to install PolyBase Query Service for External Data to use OPENROWSET, CREATE EXTERNAL TABLE, or CREATE EXTERNAL TABLE AS SELECT with the following types of external data: Parquet, Delta, Azure Blob Storage (ABS), Azure Data Lake Storage (ADLS), or S3-Compatible Object storage. |
+| Native support for CSV, Parquet, & Delta <sup>1</sup> | PolyBase Query Service for External Data installation is no longer required to use OPENROWSET, CREATE EXTERNAL TABLE, or CREATE EXTERNAL TABLE AS SELECT with the following types of external data: Parquet, Delta, Azure Blob Storage (ABS), Azure Data Lake Storage (ADLS), or S3-Compatible Object storage. |
 | Use generic ODBC data sources on Linux | For more information, see [Configure PolyBase to access external data with ODBC generic types](polybase-configure-odbc-generic.md). |
+|TDS 8.0 Support|When using [Microsoft ODBC Driver 18 for SQL Server driver](/sql/connect/odbc/windows/features-of-the-microsoft-odbc-driver-for-sql-server-on-windows).<br /><br /> TDS 8.0 is not supported for sqlserver as [external data source](/sql/t-sql/statements/create-external-data-source-transact-sql).|
 
 <sup>1</sup> On [!INCLUDE [sssql25-md](../../includes/sssql25-md.md)], PolyBase Query Service for External Data is still required to connect with other databases. For example: SQL Server, Oracle, DB2, Teradata, MongoDB, or ODBC.
 
@@ -157,7 +158,7 @@ Azure Storage connectors must be changed based on the following reference table:
 
 | External data source | From | To |
 | --- | --- | --- |
-| `Azure Blob Storage | wasb[s] | abs |
+| Azure Blob Storage | wasb[s] | abs |
 | ADLS Gen 2 | abfs[s] | adls |
 
 ## Get started

docs/sql-server/azure-arc/connect-already-enabled.md

@@ -1,26 +1,30 @@
 ---
-title: Connect SQL Server on a server already enabled by Azure Arc
+title: Connect SQL Server on a Server Already Enabled by Azure Arc
 description: Connect an instance of SQL Server to Azure Arc on a server that is already enabled by Azure Arc. Allows you to manage SQL Server centrally, as an Arc-enabled resource.
 author: anosov1960
 ms.author: sashan
 ms.reviewer: mikeray, maghan
-ms.date: 03/08/2024
+ms.date: 06/30/2025
 ms.topic: how-to
 ---
 
 # Connect your SQL Server to Azure Arc on a server already enabled by Azure Arc
 
 [!INCLUDE [sqlserver](../../includes/applies-to-version/sqlserver.md)]
 
+This article explains how to connect your SQL Server instance to Azure Arc on an Arc-enabled server. For example, you need to use this method to connect a SQL Server instance to Azure Arc at this time in US Government Virginia region, because automatic connection isn't currently available in that region. For this case, follow the steps under [Connect](#connect).
+
+If the physical or virtual server isn't connected to Azure yet, follow the steps in [Connect your SQL Server to Azure Arc](connect.md).
+
 [!INCLUDE [automatic](includes/if-manual.md)]
 
-Before you proceed, complete the [Prerequisites](prerequisites.md).
+## Prerequisites
 
-This article explains how to connect your SQL Server instance to Azure Arc on an Arc-enabled server. If the physical or virtual server isn't connected to Azure yet, follow the steps in [Connect your SQL Server to Azure Arc](connect.md).
+Verify that `Microsoft.AzureArcData` is registered in each subscription. Review instructions at [Register resource providers](prerequisites.md#register-resource-providers).
 
-If the machine with SQL Server is already connected to Azure Arc, to connect the SQL Server instances, install *Azure extension for SQL Server*. The extension is in the extension tab of "Server -Azure Arc" resource as **Azure Extension for SQL Server**.
+Review all of the prerequisites at [Prerequisites - SQL Server enabled by Azure Arc](prerequisites.md).
 
-For example, you need to use this method to connect a SQL Server instance to Azure Arc at this time in US Government Virginia region, because automatic connection is not currently available in that region. For this case, follow the steps under [Connect](#connect).
+If the machine with SQL Server is already connected to Azure Arc, to connect the SQL Server instances, install *Azure extension for SQL Server*. The extension is in the extension tab of "Server - Azure Arc" resource as **Azure Extension for SQL Server**.
 
 > [!IMPORTANT]  
 > The Azure resource with type `SQL Server - Azure Arc` representing the SQL Server instance installed on the machine uses the same region and resource group as the Azure resources for Arc-enabled servers.
@@ -35,9 +39,9 @@ To install the Azure extension for SQL Server, use the following steps:
 1. Search for the connected server with the SQL Server instance that you want to connect to Azure.
 1. Under **Extensions**, select **+ Add**.
 1. Select `Azure extension for SQL Server` and select **Next**.
-1. Specify the SQL Server edition and license type you are using on this machine. Some Arc-enabled SQL Server features are only available for SQL Server instances with Software Assurance (Paid) or with Azure pay-as-you-go. For more information, review [Manage SQL Server license type](manage-configuration.md).
+1. Specify the SQL Server edition and license type you're using on this machine. Some Arc-enabled SQL Server features are only available for SQL Server instances with Software Assurance (Paid) or with Azure pay-as-you-go. For more information, review [Configure SQL Server enabled by Azure Arc](manage-configuration.md).
 1. Specify the SQL Server instance(s) you want to exclude from registering (if you have multiple instances to skip, separate them by spaces) and select **Review + Create**.
-   :::image type="content" source="media/join/license-type-in-extension.png" alt-text="Screenshot for license type and exclude instances.":::
+   :::image type="content" source="media/join/license-type-in-extension.png" alt-text="Screenshot for license type and exclude instances." lightbox="media/join/license-type-in-extension.png":::
 1. Select **Create**.
 
 ### [PowerShell](#tab/powershell)
@@ -83,10 +87,10 @@ The extension runs continuously to detect changes in the SQL Server configuratio
 
 Go to **Azure Arc > SQL Server** and open the newly registered Arc-enabled SQL Server resource to validate.
 
-:::image type="content" source="media/join/validate-sql-server-azure-arc.png" alt-text="Screenshot of validating a connected SQL Server.":::
+:::image type="content" source="media/join/validate-sql-server-azure-arc.png" alt-text="Screenshot of validating a connected SQL Server." lightbox="media/join/validate-sql-server-azure-arc.png":::
 
-## Next steps
+## Related content
 
-- [Configure advanced data security for your SQL Server instance](configure-advanced-data-security.md)
-- [Configure best practices assessment on a [!INCLUDE [ssazurearc](../../includes/ssazurearc.md)] instance](assess.md)
+- [Protect SQL Server with Microsoft Defender for Cloud](configure-advanced-data-security.md)
+- [Configure best practices assessment for SQL Server enabled by Azure Arc](assess.md)
 - [Known issues: SQL Server enabled by Azure Arc](known-issues.md)