Merge branch 'main' of https://github.com/MicrosoftDocs/sql-docs-pr into docs-editor/copy-into-transact-sql-1751126904

Author: WilliamDAssafMSFT

.openpublishing.publish.config.json

@@ -134,12 +134,6 @@
       "branch": "master",
       "branch_mapping": {}
     },
-    {
-      "path_to_root": "azure-docs-pr",
-      "url": "https://github.com/MicrosoftDocs/azure-docs-pr",
-      "branch": "main",
-      "branch_mapping": {}
-    },
     {
       "path_to_root": "azure-compute-docs-pr",
       "url": "https://github.com/MicrosoftDocs/azure-compute-docs-pr",
@@ -199,4 +193,4 @@
     ".openpublishing.redirection.stretch-database.json",
     ".openpublishing.redirection.visual-studio-code-extensions.json"
   ]
-}
+}

.openpublishing.redirection.json

@@ -1,5 +1,125 @@
 {
   "redirections": [
+    {
+      "source_path": "docs/dma/dma-assess-sql-data-estate-to-sqldb-commandline.md",
+      "redirect_url": "/previous-versions/sql/dma/dma-assess-sql-data-estate-to-sqldb-commandline",
+      "redirect_document_id": false,
+      "monikers": [
+        "sql-server-ver16"
+      ]
+    },
+    {
+      "source_path": "docs/dma/dma-assess-sql-data-estate-to-sqldb.md",
+      "redirect_url": "/previous-versions/sql/dma/dma-assess-sql-data-estate-to-sqldb",
+      "redirect_document_id": false,
+      "monikers": [
+        "sql-server-ver16"
+      ]
+    },
+    {
+      "source_path": "docs/dma/dma-assess-ssis.md",
+      "redirect_url": "/previous-versions/sql/dma/dma-assess-ssis",
+      "redirect_document_id": false,
+      "monikers": [
+        "sql-server-ver16"
+      ]
+    },
+    {
+      "source_path": "docs/dma/dma-assesssqlonprem.md",
+      "redirect_url": "/previous-versions/sql/dma/dma-assesssqlonprem",
+      "redirect_document_id": false,
+      "monikers": [
+        "sql-server-ver16"
+      ]
+    },
+    {
+      "source_path": "docs/dma/dma-bestpractices.md",
+      "redirect_url": "/previous-versions/sql/dma/dma-bestpractices",
+      "redirect_document_id": false,
+      "monikers": [
+        "sql-server-ver16"
+      ]
+    },
+    {
+      "source_path": "docs/dma/dma-commandline.md",
+      "redirect_url": "/previous-versions/sql/dma/dma-commandline",
+      "redirect_document_id": false,
+      "monikers": [
+        "sql-server-ver16"
+      ]
+    },
+    {
+      "source_path": "docs/dma/dma-configurationsettings.md",
+      "redirect_url": "/previous-versions/sql/dma/dma-configurationsettings",
+      "redirect_document_id": false,
+      "monikers": [
+        "sql-server-ver16"
+      ]
+    },
+    {
+      "source_path": "docs/dma/dma-diagnostic-data-collection.md",
+      "redirect_url": "/previous-versions/sql/dma/dma-diagnostic-data-collection",
+      "redirect_document_id": false,
+      "monikers": [
+        "sql-server-ver16"
+      ]
+    },
+    {
+      "source_path": "docs/dma/dma-migrateonpremsql.md",
+      "redirect_url": "/previous-versions/sql/dma/dma-migrateonpremsql",
+      "redirect_document_id": false,
+      "monikers": [
+        "sql-server-ver16"
+      ]
+    },
+    {
+      "source_path": "docs/dma/dma-migrateonpremsqltosqldb.md",
+      "redirect_url": "/previous-versions/sql/dma/dma-migrateonpremsqltosqldb",
+      "redirect_document_id": false,
+      "monikers": [
+        "sql-server-ver16"
+      ]
+    },
+    {
+      "source_path": "docs/dma/dma-migrateserverlogins.md",
+      "redirect_url": "/previous-versions/sql/dma/dma-migrateserverlogins",
+      "redirect_document_id": false,
+      "monikers": [
+        "sql-server-ver16"
+      ]
+    },
+    {
+      "source_path": "docs/dma/dma-overview.md",
+      "redirect_url": "/previous-versions/sql/dma/dma-overview",
+      "redirect_document_id": false,
+      "monikers": [
+        "sql-server-ver16"
+      ]
+    },
+    {
+      "source_path": "docs/dma/dma-save-load-assessments.md",
+      "redirect_url": "/previous-versions/sql/dma/dma-save-load-assessments",
+      "redirect_document_id": false,
+      "monikers": [
+        "sql-server-ver16"
+      ]
+    },
+    {
+      "source_path": "docs/dma/dma-sku-recommend-sql-db.md",
+      "redirect_url": "/previous-versions/sql/dma/dma-sku-recommend-sql-db",
+      "redirect_document_id": false,
+      "monikers": [
+        "sql-server-ver16"
+      ]
+    },
+    {
+      "source_path": "docs/dma/dma-whats-new.md",
+      "redirect_url": "/previous-versions/sql/dma/dma-whats-new",
+      "redirect_document_id": false,
+      "monikers": [
+        "sql-server-ver16"
+      ]
+    },
     {
       "source_path": "azure-sql/database/saas-dbpertenant-dr-geo-replication.md",
       "redirect_url": "/previous-versions/sql/database/saas-dbpertenant-dr-geo-replication",
@@ -47630,6 +47750,11 @@
       "redirect_url": "/previous-versions/sql/2014/tools/sqlagent90-application",
       "redirect_document_id": false
     },
+    {
+      "source_path": "docs/tools/sqlagent90-application.md",
+      "redirect_url": "/sql/tools/sqlagent-application",
+      "redirect_document_id": false
+    },
     {
       "source_path": "docs/2014/tools/sqlcmd-utility.md",
       "redirect_url": "/previous-versions/sql/2014/tools/sqlcmd-utility",
@@ -47900,6 +48025,11 @@
       "redirect_url": "/previous-versions/sql/2014/tools/configuration-manager/sql-server-browser-service",
       "redirect_document_id": false
     },
+    {
+      "source_path": "docs/tools/configuration-manager/sql-server-browser-service.md",
+      "redirect_url": "/sql/database-engine/configure-windows/sql-server-browser-service-database-engine-and-ssas",
+      "redirect_document_id": false
+    },
     {
       "source_path": "docs/2014/tools/configuration-manager/sql-server-browser-sql-server-configuration-manager.md",
       "redirect_url": "/previous-versions/sql/2014/tools/configuration-manager/sql-server-browser-sql-server-configuration-manager",

azure-sql/azure-hybrid-benefit.md

@@ -30,7 +30,7 @@ You can enable the Azure Hybrid Benefit for Azure SQL Database by using the Azur
 
 For Azure SQL Database, Azure Hybrid Benefit is only available when using the provisioned compute tier of the [vCore-based purchasing model](database/service-tiers-vcore.md). Azure Hybrid Benefit doesn't apply to the [DTU-based purchasing model](database/service-tiers-dtu.md) or the [serverless compute tier](database/serverless-tier-overview.md).
 
-#### [Portal](#tab/azure-portal)
+#### [Azure portal](#tab/azure-portal)
 
 To set or update the license type to the Azure Hybrid Benefit by using the Azure portal:
 
@@ -65,7 +65,7 @@ To set or update the license type to the Azure Hybrid Benefit by using the REST
 
 You can enable the Azure Hybrid Benefit for Azure SQL Managed Instance by using the Azure portal, PowerShell, Azure CLI, or REST API.
 
-#### [Portal](#tab/azure-portal)
+#### [Azure portal](#tab/azure-portal)
 
 To set or update the license type to the Azure Hybrid Benefit by using the Azure portal:
 

azure-sql/azure-sql-iaas-vs-paas-what-is-overview.md

@@ -190,4 +190,3 @@ For pricing:
 
 To migrate:
 - [Migrate to Azure SQL](migration-guides/index.yml)
-- [Identify the right SKU for your on-premises database](/sql/dma/dma-sku-recommend-sql-db/)

azure-sql/database-watcher-data.md

@@ -5,7 +5,7 @@ description: A detailed description of SQL monitoring data collected by database
 author: lcwright
 ms.author: lancewright
 ms.reviewer: dfurman
-ms.date: 05/04/2025
+ms.date: 07/08/2025
 ms.service: azure-sql
 ms.subservice: monitoring
 ms.topic: conceptual
@@ -101,7 +101,10 @@ END CATCH;
 
 To avoid concurrency conflicts such as blocking and deadlocks between data collection and database workloads running on your Azure SQL resources, the monitoring queries use short [lock timeouts](/sql/relational-databases/sql-server-transaction-locking-and-row-versioning-guide#customizing-the-lock-time-out) and low [deadlock priority](/sql/t-sql/statements/set-deadlock-priority-transact-sql). If there is a concurrency conflict, priority is given to the application workload queries.
 
-You might observe gaps in the collected data if the overall resource utilization is high, or if concurrency conflicts occur. In these cases, monitoring queries might be deprioritized in favor of application workloads.
+You might observe gaps in the collected data in the following scenarios:
+
+- If the overall resource utilization is high, or if concurrency conflicts between monitoring queries and application workloads occur. In these cases, monitoring queries are deprioritized in favor of application workloads.
+- If you have automation that terminates long-running sessions. To avoid gaps in collected data, exclude any session where the `program_name` column in the [sys.dm_exec_sessions](/sql/relational-databases/system-dynamic-management-views/sys-dm-exec-sessions-transact-sql) system view is `SQLExternalMonitoring` or `x_ms_reserved_sql_external_monitoring`.
 
 ### Data collection in elastic pools
 

azure-sql/database/ai-artificial-intelligence-intelligent-applications.md

@@ -5,6 +5,7 @@ author: WilliamDAssafMSFT
 ms.author: wiassaf
 ms.reviewer: damauri, josephsack, randolphwest, mathoma
 ms.date: 05/06/2025
+ms.update-cycle: 180-days
 ms.service: azure-sql-database
 ms.topic: conceptual
 ms.collection:
@@ -195,7 +196,7 @@ End-to-end examples:
 
 [Semantic Kernel is an open-source SDK](/semantic-kernel/overview/) that lets you easily build agents that can call your existing code. As a highly extensible SDK, you can use Semantic Kernel with models from OpenAI, Azure OpenAI, Hugging Face, and more. By combining your existing C#, Python, and Java code with these models, you can build agents that answer questions and automate processes. 
 
-- [Microsoft.SemanticKernel.Connectors.SqlServer](https://github.com/microsoft/semantic-kernel/tree/main/dotnet/src/Connectors/Connectors.Memory.SqlServer)
+- [Microsoft.SemanticKernel.Connectors.SqlServer](/dotnet/api/microsoft.semantickernel.connectors.sqlserver)
 
 An example of how easily Semantic Kernel helps to build AI-enabled solution is here:
 

azure-sql/database/alerts-create.md

@@ -49,7 +49,7 @@ You can configure and get information about alert rules using:
 - [PowerShell](/azure/azure-monitor/alerts/alerts-create-rule-cli-powershell-arm#create-a-new-alert-rule-using-powershell)
 - [Command-line interface (CLI)](/azure/azure-monitor/alerts/alerts-create-rule-cli-powershell-arm#create-a-new-alert-rule-using-the-cli)
 - [ARM template](/azure/azure-monitor/alerts/alerts-create-rule-cli-powershell-arm#create-a-new-alert-rule-using-an-arm-template)
-- [Azure Monitor REST API](/rest/api/monitor/alertrules)
+- [Azure Monitor REST API](/rest/api/monitor/alertsmanagement/alert-processing-rules)
 
 ## Get started with a new alert rule in the Azure portal
 

azure-sql/database/always-encrypted-with-secure-enclaves-landing.yml

@@ -120,7 +120,7 @@ landingContent:
           - text: Inside Azure Datacenter Architecture with Mark Russinovich
             url: https://youtu.be/69PrhWQorEM?t=4523
           - text: A webinar including a section on secure enclaves
-            url: https://info.microsoft.com/ww-ondemand-azure-webinar-series-four-ways-to-take-your-data-security-to-the-next-level.html
+            url: https://info.microsoft.com/en-us-ondemand-SimplifyandautomateresearchcomplianceresponsibilitieswithAzure-none.html
 
   # Card
   - title: Query columns

azure-sql/database/auditing-analyze-audit-logs.md

@@ -4,15 +4,15 @@ titleSuffix: Azure SQL Database & Azure Synapse Analytics
 description: Use Auditing to analyze logs in Log Analytics, Event Hubs, or through an Azure storage account.
 author: sravanisaluru
 ms.author: srsaluru
-ms.reviewer: mathoma
-ms.date: 06/10/2025
+ms.reviewer: mathoma, vanto
+ms.date: 07/09/2025
 ms.service: azure-sql-database
 ms.subservice: security
 ms.topic: how-to
 ---
 # Use Auditing to analyze audit logs and reports
 
-[!INCLUDE[appliesto-sqldb-asa](../includes/appliesto-sqldb-asa.md)]
+[!INCLUDE [appliesto-sqldb-asa](../includes/appliesto-sqldb-asa.md)]
 
 This article provides an overview of analyzing audit logs using Auditing for [Azure SQL Database](sql-database-paas-overview.md) and [Azure Synapse Analytics](/azure/synapse-analytics/sql-data-warehouse/sql-data-warehouse-overview-what-is). You can use Auditing to analyze audit logs stored in:
 
@@ -26,7 +26,7 @@ If you chose to write audit logs to Log Analytics:
 
 1. Use the [Azure portal](https://portal.azure.com).
 1. Go to the relevant database resource.
-1. At the top of the database's **Auditing** page, select **View audit logs**.
+1. At the top of the database's **Auditing** page, select **View audit logs** to display a sample of audit logs with a limited set of fields that cover activity from up to 2 hours prior to the selected **End Time** (which defaults to 'now'):
 
    :::image type="content" source="media/auditing-analyze-audit-logs/view-audit-logs.png" alt-text="Screenshot of the Auditing menu in the Azure portal where you can select the View audit logs option." lightbox="media/auditing-analyze-audit-logs/view-audit-logs.png":::
 
@@ -69,7 +69,7 @@ If you chose to write audit logs to an Azure storage account, there are several
 
   1. The merged file opens in SSMS, where you can view and analyze it, as well as export it to an XEL or CSV file, or to a table.
 
-- Use Power BI. You can view and analyze audit log data in Power BI. For more information and to access a downloadable template, see [Blog: Analyze audit log data in Power BI](https://techcommunity.microsoft.com/blog/azuredbsupport/sql-azure-blob-auditing-basic-power-bi-dashboard/368895).
+- Use Power BI. You can view and analyze audit log data in Power BI. For more information, see [Using Azure Log Analytics in Power BI](/power-bi/transform-model/log-analytics/desktop-log-analytics-overview).
 - Download log files from your Azure Storage blob container via the portal or by using a tool such as [Azure Storage Explorer](https://azure.microsoft.com/products/storage/storage-explorer).
   - After you have downloaded a log file locally, double-click the file to open, view, and analyze the logs in SSMS.
   - You can also download multiple files simultaneously in Azure Storage Explorer. To do so, right-click a specific subfolder and select **Save as** to save in a local folder.

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)