Merge branch 'docs-editor/move-resources-1758244050' of https://github.com/anosov1960/sql-docs-pr into docs-editor/move-resources-1758244050

Author: MikeRayMSFT

.openpublishing.redirection.json

@@ -10640,6 +10640,26 @@
         "sql-server-ver16"
       ]
     },
+    {
+      "source_path": "docs/sql-server/artificial-intelligence-intelligent-applications.md",
+      "redirect_url": "/sql/sql-server/ai/artificial-intelligence-intelligent-applications",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "docs/sql-server/artificial-intelligence-intelligent-applications-faq.md",
+      "redirect_url": "/sql/sql-server/ai/artificial-intelligence-intelligent-applications-faq",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "docs/relational-databases/vectors/vectors-sql-server.md",
+      "redirect_url": "/sql/sql-server/ai/vectors",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "docs/relational-databases/vectors/vectors-faq.md",
+      "redirect_url": "/sql/sql-server/ai/vectors-faq",
+      "redirect_document_id": false
+    },
     {
       "source_path": "docs/sql-server/ai-artificial-intelligence-intelligent-applications.md",
       "redirect_url": "/sql/sql-server/artificial-intelligence-intelligent-applications",

azure-sql/database-watcher-faq.yml

@@ -5,7 +5,7 @@ metadata:
   description: Frequently asked questions about database watcher for Azure SQL
   author: lcwright
   ms.author: lancewright
-  ms.date: 05/04/2025
+  ms.date: 09/29/2025
   ms.reviewer: wiassaf, dfurman
   ms.service: azure-sql
   ms.subservice: monitoring
@@ -64,7 +64,7 @@ sections:
 
       - question: |
           Does it support cross-subscription and cross-tenant monitoring?
-        answer: The watcher and the SQL targets it monitors can be in different subscriptions within the same Microsoft Entra ID tenant. Similarly, if the watcher is using a database on an Azure Data Explorer cluster as its data store, the cluster must be in any subscription within the same tenant as the watcher. If you want to monitor SQL targets in multiple tenants using a single data store, create a watcher in each tenant, and use a database in either [Real-Time Analytics](/fabric/real-time-analytics/overview) or on a [free Azure Data Explorer cluster](/azure/data-explorer/start-for-free) as the data store for all watchers. For more information, see [Monitor large estates](database-watcher-manage.md#monitor-large-estates).
+        answer: The watcher and the SQL target it monitors can be in different subscriptions within the same Microsoft Entra ID tenant. Similarly, if the watcher is using a database on an Azure Data Explorer cluster as its data store, the cluster must be in any subscription within the same tenant as the watcher. If you want to monitor SQL targets in multiple tenants using a single data store, create a watcher in each tenant, and use a database in either [Real-Time Analytics](/fabric/real-time-analytics/overview) or on a [free Azure Data Explorer cluster](/azure/data-explorer/start-for-free) as the data store for all watchers. For more information, see [Monitor large estates](database-watcher-manage.md#monitor-large-estates).
 
   - name: Watcher
     questions:
@@ -110,6 +110,10 @@ sections:
           Can I export SQL monitoring data from Azure Data Explorer?
         answer: Yes. For example, you can [export](/azure/data-explorer/kusto/management/data-export) data to Azure storage, a data lake, or a SQL Server or an Azure SQL database.
 
+      - question: |
+          What happens to the collected SQL monitoring data when I delete a SQL target?
+        answer: The data for the deleted SQL targets is retained in the data store according to the [retention policy](database-watcher-manage.md#manage-data-retention) for the database or table, and can be accessed via the dashboards and queries for historical purposes. For more information about deleting collected data from the data store before the retention period expires, see [Delete data](/kusto/concepts/delete-data). The summary page of the watcher uses the data in the data store, and shows recently deleted SQL targets for up to 72 hours.
+
   - name: Data collection
     questions:
       - question: |

azure-sql/database/active-geo-replication-overview.md

@@ -16,7 +16,7 @@ ms.custom:
 
 [!INCLUDE [appliesto-sqldb](../includes/appliesto-sqldb.md)]
 
-This article provides and overview of the active geo-replication feature for [Azure SQL Database](sql-database-paas-overview.md), which lets you continuously replicate data from a primary database to a readable secondary database. The readable secondary database might be in the same Azure region as the primary, or, more commonly, in a different region. This kind of readable secondary database is also known as a geo-secondary or geo-replica.
+This article provides an overview of the active geo-replication feature for [Azure SQL Database](sql-database-paas-overview.md), which lets you continuously replicate data from a primary database to a readable secondary database. The readable secondary database might be in the same Azure region as the primary, or, more commonly, in a different region. This kind of readable secondary database is also known as a geo-secondary or geo-replica.
 
 Active geo-replication is configured per database. To fail over a group of databases, or if your application requires a stable connection endpoint, consider [Failover groups](failover-group-sql-db.md) instead.
 

azure-sql/database/analyze-prevent-deadlocks.md

@@ -5,7 +5,7 @@ description: Learn how to analyze deadlocks and prevent them from reoccurring in
 author: rwestMSFT
 ms.author: randolphwest
 ms.reviewer: mathoma, dfurman, wiassaf
-ms.date: 01/28/2025
+ms.date: 09/23/2025
 ms.service: azure-sql-database
 ms.subservice: performance
 ms.topic: troubleshooting-general
@@ -19,7 +19,7 @@ ms.custom:
 
 [!INCLUDE [appliesto-sqldb-fabricsqldb](../includes/appliesto-sqldb-fabricsqldb.md)]
 
-This article teaches you how to identify deadlocks, use deadlock graphs and Query Store to identify the queries in the deadlock, and plan and test changes to prevent deadlocks from reoccurring. This article applies to Azure SQL Database and Fabric SQL database, which shares many features of Azure SQL Database.
+This article teaches you how to identify deadlocks, use deadlock graphs and Query Store to identify the queries in the deadlock, and plan and test changes to prevent deadlocks from reoccurring. This article applies to Azure SQL Database and SQL database in Fabric, which shares many features of Azure SQL Database.
 
 This article focuses on identifying and analyzing deadlocks due to lock contention. Learn more about other types of deadlocks in [resources that can deadlock](/sql/relational-databases/sql-server-deadlocks-guide#deadlock_resources).
 
@@ -118,7 +118,7 @@ Learn more about each of these approaches in the [Prevent a deadlock from reoccu
 
 In this article, we use the `AdventureWorksLT` sample database to set up alerts for deadlocks, cause an example deadlock, analyze the deadlock graph for the example deadlock, and test changes to prevent the deadlock from reoccurring.
 
-We use the [SQL Server Management Studio](/sql/ssms/download-sql-server-management-studio-ssms) (SSMS) client in this article, as it contains functionality to display deadlock graphs in an interactive visual mode. You can use other clients such as [Azure Data Studio](/azure-data-studio/download-azure-data-studio) to follow along with the examples, but you might only be able to view deadlock graphs as XML.
+We use the [SQL Server Management Studio](/sql/ssms/download-sql-server-management-studio-ssms) (SSMS) client in this article, as it contains functionality to display deadlock graphs in an interactive visual mode. You can use other clients such as [Azure Data Studio](/azure-data-studio/download-azure-data-studio), the [MSSQL extension for Visual Studio Code](/sql/tools/visual-studio-code-extensions/mssql/mssql-extension-visual-studio-code), [sqlcmd](/sql/tools/sqlcmd/sqlcmd-utility), or your favorite T-SQL querying tool to follow along with the examples, but you might only be able to view deadlock graphs as XML.
 
 ### Create the AdventureWorksLT database
 
@@ -128,13 +128,13 @@ For detailed instructions on how to create `AdventureWorksLT` with the Azure por
 
 ### Set up deadlock alerts in the Azure portal
 
-To set up alerts for deadlock events, follow the steps in the article [Create alerts for Azure SQL Database and Azure Synapse Analytics using the Azure portal](alerts-create.md).
+To set up alerts for deadlock events, follow the steps in the article [Create alerts for Azure SQL Database using the Azure portal](alerts-create.md).
 
 Select **Deadlocks** as the signal name for the alert. Configure the **Action group** to notify you using the method of your choice, such as the **Email/SMS/Push/Voice** action type.
 
 ## Collect deadlock graphs in Azure SQL Database with Extended Events
 
-Deadlock graphs are a rich source of information regarding the processes and locks involved in a deadlock. To collect deadlock graphs with Extended Events (XEvents) in Azure SQL Database, capture the `sqlserver.database_xml_deadlock_report` event.
+Deadlock graphs are a rich source of information regarding the processes and locks involved in a deadlock. To collect deadlock graphs with Extended Events (XEvents) in Azure SQL Database and SQL database in Fabric, capture the `sqlserver.database_xml_deadlock_report` event.
 
 You can collect deadlock graphs with XEvents using either the [ring buffer target](xevent-code-ring-buffer.md) or an [event file target](xevent-code-event-file.md). Considerations for selecting the appropriate target type are summarized in the following table:
 
@@ -184,7 +184,7 @@ To create an XEvents session that writes to an event file target, we:
 To configure an Azure Storage container, first create or select an existing Azure Storage account, then create the container. Generate a Shared Access Signature (SAS) token for the container. This section describes completing this process in the Azure portal.
 
 > [!NOTE]  
-> If you wish to create and configure the Azure Storage blob container with PowerShell, see [Event File target code for extended events in Azure SQL Database](xevent-code-event-file.md). Alternately, you might find it convenient to [Use Azure Storage Explorer](#use-azure-storage-explorer) to create and configure the Azure Storage blob container instead of using the Azure portal.
+> If you wish to create and configure the Azure Storage blob container with PowerShell, see [Event File target code for extended events in Azure SQL Database and SQL database in Fabric](xevent-code-event-file.md). Alternately, you might find it convenient to [Use Azure Storage Explorer](#use-azure-storage-explorer) to create and configure the Azure Storage blob container instead of using the Azure portal.
 
 #### Create or select an Azure Storage account
 
@@ -228,7 +228,7 @@ From the container page in the Azure portal:
 
 ### Create a database scoped credential
 
-Connect to your database in Azure SQL Database with SSMS to run the following steps.
+Connect to your database with SSMS to run the following steps.
 
 To create a database scoped credential, you must first create a [database master key](/sql/t-sql/statements/create-master-key-transact-sql) (DMK) in the database if one doesn't exist.
 
@@ -688,7 +688,7 @@ Resources are represented by rectangles in the visual representation of the dead
 :::image type="content" source="media/analyze-prevent-deadlocks/deadlock-graph-resource-list.png" alt-text="Screenshot of a deadlock graph, displayed visually in SSMS. Rectangles show the resources that are involved in the deadlock." lightbox="media/analyze-prevent-deadlocks/deadlock-graph-resource-list.png":::
 
 > [!NOTE]  
-> Database names are represented as GUIDs (**uniqueidentifier**) in deadlock graphs for databases in Azure SQL Database. This is the `physical_database_name` for the database listed in the [sys.databases](/sql/relational-databases/system-catalog-views/sys-databases-transact-sql) and [sys.dm_user_db_resource_governance](/sql/relational-databases/system-dynamic-management-views/sys-dm-user-db-resource-governor-azure-sql-database) dynamic management views.
+> Database names are represented as GUIDs (**uniqueidentifier**) in deadlock graphs for databases in Azure SQL Database and SQL database in Fabric. This is the `physical_database_name` for the database listed in the [sys.databases](/sql/relational-databases/system-catalog-views/sys-databases-transact-sql) and [sys.dm_user_db_resource_governance](/sql/relational-databases/system-dynamic-management-views/sys-dm-user-db-resource-governor-azure-sql-database) dynamic management views.
 
 In this example deadlock:
 

azure-sql/database/automated-backups-overview.md

@@ -5,7 +5,7 @@ description: Learn how Azure SQL Database automatically backs up all databases a
 author: WilliamDAssafMSFT
 ms.author: wiassaf
 ms.reviewer: mathoma, danil, dinethi
-ms.date: 03/03/2025
+ms.date: 09/25/2025
 ms.service: azure-sql-database
 ms.subservice: backup-restore
 ms.topic: conceptual
@@ -144,7 +144,7 @@ For information on recovery times, see [RTO and RPO](business-continuity-high-av
 | **Types of SQL backup** | Full, differential, log. | Most recent geo-replicated copies of PITR backups. | Only the full backups. |
 | **Retention** | 7 days by default, configurable between 1 and 35 days (except Basic databases, which are configurable between 1 and 7 days). | Enabled by default, same as source.<sup>2</sup>| Not enabled by default. Retention is up to 10 years. |
 | **Azure Storage**  | Geo-redundant by default. You can optionally configure zone-redundant or locally redundant storage. | Available when PITR backup storage redundancy is set to geo-redundant. Not available when PITR backup storage is zone-redundant or locally redundant. | Geo-redundant by default. You can configure zone-redundant or locally redundant storage. |
-| **Configure backups as [immutable](/azure/storage/blobs/immutable-storage-overview)** | Not supported | Not supported | Not supported | 
+| **Configure backups as [immutable](/azure/storage/blobs/immutable-storage-overview)** | Not supported | Not supported | [Supported](backup-immutability.md) (in Preview) | 
 | **Restoring a new database in the same region** | Supported | Supported | Supported |
 | **Restoring a new database in another region** | Not supported | Supported in any Azure region | Supported in any Azure region |
 | **Restoring a new database in another subscription** |  Not supported  |  Not supported<sup>3</sup> | Not supported<sup>3</sup> |

azure-sql/database/backup-immutability-legal-hold.md

@@ -0,0 +1,101 @@
+---
+title: Configure Legal Hold Backup Immutability for Long-Term Retention Backups
+titleSuffix: Azure SQL Database
+description: Learn how to configure legal hold backup immutability for long-term retention backups.
+author: WilliamDAssafMSFT
+ms.author: wiassaf
+ms.reviewer: dinethi
+ms.date: 09/29/2025
+ms.service: azure-sql-database
+ms.subservice: backup-restore
+ms.topic: how-to
+monikerRange: "=azuresql || =azuresql-db"
+---
+# Configure legal hold backup immutability for long-term retention backups in Azure SQL Database
+
+[!INCLUDE [appliesto-sqldb](../includes/appliesto-sqldb.md)]
+
+In this article, learn how to configure **legal hold backup immutability** for long-term retention (LTR) backups in Azure SQL Database.
+
+[Backup immutability for long-term retention backups](backup-immutability.md) is available in two modes: time-based immutability and legal hold immutability.
+
+Once locked with legal hold backup immutability, backups can't be deleted or modified until legal hold backup immutability is manually removed.
+
+## Prerequisites
+
+1. An active Azure subscription.
+1. An existing Azure SQL Database.
+1. Existing long-term retention (LTR) backups.
+
+## Permissions
+
+You need to be a member of the Subscription Contributor role or higher permissions for the logical server of the Azure SQL Database to configure backup immutability for LTR backups and delete LTR backups.
+
+For permissions to view, managed, and delete LTR backups, see [Manage Azure SQL Database long-term backup retention](long-term-backup-retention-configure.md#permissions).
+
+## Enable legal hold immutability for existing LTR backups
+
+You can enable legal hold immutability on any existing backups. These backups are protected from any edits or deletes until the legal hold is explicitly removed.
+
+> [!IMPORTANT]
+> Legal hold backup immutability can apply only to existing backups. To make future backups automatically immutable, instead use [time-based immutability](backup-immutability-time-based.md).
+
+#### [Azure portal](#tab/azure-portal)
+
+**To enable legal hold backup immutability from the Azure portal:**
+
+1. Navigate to your Azure SQL Database logical server.
+1. Under **Data management**, navigate to the **Backups** tab.
+1. For the desised database, under **Available LTR Backups**, select **Manage**.
+1. Select one or more available backups.
+1. Select **Enable Legal Hold** to enable legal hold immutability.
+
+   :::image type="content" source="media/backup-immutability-legal-hold/enable-legal-hold.png" alt-text="Screenshot from the Azure portal showing how to enable Legal Hold backup immutability on a backup." lightbox="media/backup-immutability-legal-hold/enable-legal-hold.png":::
+
+#### [PowerShell](#tab/azure-powershell)
+
+**To enable legal hold backup immutability with PowerShell:**
+
+```powershell
+Set-AzSqlDatabaseLongTermRetentionBackupLegalHold
+    -Location southeastasia
+    -ServerName myAzureSQL
+    -DatabaseName mysqldb
+    -BackupName 'myLTRbackup-1-24'
+```
+
+---
+
+## Remove legal hold immutability
+
+Legal hold immutability on specific backups can be disabled as follows:
+
+#### [Azure portal](#tab/azure-portal)
+
+**To remove legal hold immutability from a backup from the Azure portal:**
+
+1. Navigate to your Azure SQL Database logical server.
+1. Under **Data management**, navigate to the **Backups** tab.
+1. Go to the **Manage** section under **Available LTR Backups**.
+1. Select one or more backups.
+1. Select **Disable Legal Hold** to remove legal hold immutability.
+
+#### [PowerShell](#tab/azure-powershell)
+
+**To remove legal hold immutability from a backup with PowerShell:**
+
+```powershell
+Remove-AzSqlDatabaseLongTermRetentionBackupLegalHold
+    -Location southeastasia
+    -ServerName myAzureSQL
+    -DatabaseName mysqldb
+    -BackupName 'myLTRbackup-1-24'
+```
+
+---
+
+## Related content
+
+- [Configure time-based backup immutability for long-term retention backups in Azure SQL Database](backup-immutability-time-based.md)
+- [Backup immutability for long-term retention backups in Azure SQL Database](backup-immutability.md)
+- [Automated backups in Azure SQL Database](automated-backups-overview.md)