Merge pull request #36003 from MashaMSFT/202512_dbmigts

Troubleshoot db migration in Azure Arc

Author: JamesJBarnett

azure-sql/managed-instance/failover-group-configure-sql-mi.md

@@ -478,7 +478,7 @@ To avoid problems from a lower service tier or under-resourced geo-secondary get
 - You can scale the primary and secondary instance up or down to a different compute size within the same service tier or to a different service tier. 
 - When scaling up within the same service tier, scale up the geo-secondary first, and then scale up the primary.
 - When scaling down within the same service tier, reverse the order: scale down the primary first, and then scale down the secondary. 
-- Follow the same sequence when you change the configuration of your instance. If you're scaling resources up, do so on the secondary first. If you're scaling down, do so the primary first. This applies to the following instance configuration changes: 
+- Follow the same sequence when you change the configuration of your instance. If you're scaling resources up, do so on the secondary first. If you're scaling down, do so on the primary first. This applies to the following instance configuration changes: 
   - Upgrading or downgrading the service tier. 
   - Changing the number of vCores.
   - Scaling the storage size.

azure-sql/managed-instance/managed-instance-link-migrate.md

@@ -88,11 +88,14 @@ After you've cut over to the SQL managed instance target, monitor your applicati
 
 For details, review [post-migration](../migration-guides/managed-instance/sql-server-to-managed-instance-guide.md#post-migration). 
 
-## Reverse migrate (SQL Server 2022)
+## Reverse a migration
 
-Starting with SQL Server 2022 CU10, you can configure a link with Azure SQL Managed Instance as the initial primary and SQL Server as the secondary. This capability allows you to reverse migrate from Azure SQL Managed Instance to SQL Server 2022.
+Reverse migration back to SQL Server from Azure SQL Managed Instance might be supported depending on the [update policy](/azure/azure-sql/managed-instance/update-policy) of your SQL managed instance. For example: 
+- [SQL Server 2022 update policy](/azure/azure-sql/managed-instance/update-policy#sql-server-2022-update-policy): Databases from instances configured with the **SQL Server 2022** update policy can be restored back to SQL Server 2022 instances.
+- [SQL Server 2025 update policy](/azure/azure-sql/managed-instance/update-policy#sql-server-2025-update-policy): Databases from instances configured with the **SQL Server 2025** update policy can be restored back to SQL Server 2025 instances.
+- [Always-up-to-date update policy](/azure/azure-sql/managed-instance/update-policy#always-up-to-date-update-policy): Databases from instances configured with the **Always-up-to-date** update policy can't be restored back to SQL Server.
 
-To reverse a migration, follow the same steps to configure the link, but start the process with the SQL Managed Instance as your migration source, and the SQL Server 2022 instance as the migration target. 
+If your source SQL Server version is earlier than SQL Server 2022, reverse migration isn't possible. When your database is migrated to SQL Managed Instance, it undergoes an internal upgrade to a newer database version that isn't compatible with earlier SQL Server versions. Reverse migration database compatibility is only available when SQL Managed instance is configured with the corresponding update policy.
 
 ## Related content
 

docs/relational-databases/extended-events/media/use-the-ssms-xe-profiler/start-feed.png

@@ -1,10 +1,10 @@
 ---
-title: "Use the SSMS XEvent Profiler"
+title: Use the SSMS XEvent Profiler
 description: The XEvent Profiler displays a live viewer of extended events. Learn why to use this profiler, key features, and how to get started viewing extended events.
 author: erinstellato-ms
 ms.author: erinstellato
-ms.reviewer: mikeray
-ms.date: 10/02/2016
+ms.reviewer: mikeray, mathoma
+ms.date: 12/09/2025
 ms.service: sql
 ms.subservice: xevents
 ms.topic: tutorial
@@ -13,39 +13,64 @@ helpviewer_keywords:
   - "extended events [SQL Server], system_health session"
   - "system_health session [SQL Server extended events]"
   - "system health session [SQL Server extended events]"
-monikerRange: ">=sql-server-2016||>=sql-server-linux-2017"
+monikerRange: ">=sql-server-2016 || >=sql-server-linux-2017"
 ---
 # Use the SSMS XEvent Profiler
+
 [!INCLUDE [SQL Server](../../includes/applies-to-version/sql-asdbmi.md)]
 
 The XEvent Profiler is a SQL Server Management Studio (SSMS) feature that displays a live viewer window of Extended Events. This overview describes the reasons for using this profiler, key features, and instructions to get started viewing Extended Events.
 
 ## Why would I use the XEvent Profiler?
+
 Unlike SQL Profiler, XEvent profiler is directly integrated into SSMS and is built on top of the scalable Extended Events technology in the SQL engine. This feature enables quick access to a live streaming view of diagnostics events on the SQL Server. This view can be customized and those customizations can be shared with other SSMS users as a .viewsettings file. The session created by XE Profiler is less intrusive to the running SQL Server than a similar SQL trace would be when using SQL Profiler. This session can be customized by the user as well, using the existing XE session properties UI or by Transact-SQL.
 
 ## Prerequisites
+
 This feature is only available on SQL Server Management Studio (SSMS) v17.3 or later. Install the latest version of [SQL Server Management Studio (SSMS)](/ssms/install/install).
 
-## <a id="getting-started"></a>Getting Started
+<a id="getting-started"></a>
+
+## Getting started
+
 To access the XEvent Profiler, follow these steps:
 
 1. Open **SQL Server Management Studio**.
 
-2. Connect to an instance of the SQL Server Database Engine or localhost.
+1. Connect to an instance of the SQL Server Database Engine or localhost.
+
+1. In Object Explorer, find the XE Profiler menu item and expand it by selecting the '+' sign.
+
+   :::image type="content" source="media/use-the-ssms-xe-profiler/xevents-xe-profiler-menu.png" alt-text="Screenshot of the XEProfiler Menu.":::
+
+1. Double-click **Standard** if you want to view all events in this session. Select **T-SQL** if you want to view the logged SQL statements. If a session is not already created, a session is created for you.
+
+   :::image type="content" source="media/use-the-ssms-xe-profiler/xevents-xe-profiler-start-session.png" alt-text="Screenshot of the XEProfiler Session." lightbox="media/use-the-ssms-xe-profiler/xevents-xe-profiler-start-session.png":::
+
+1. You can now view events captured by the session.
+
+   :::image type="content" source="media/use-the-ssms-xe-profiler/xevents-xe-profiler-start-viewer.png" alt-text="Screenshot of the XEProfiler Viewer." lightbox="media/use-the-ssms-xe-profiler/xevents-xe-profiler-start-viewer.png":::
+
+## Stop and start the session
+
+To start the session, either select **Start data feed** from the **Extended Events** menu in the Live Data Viewer or use the green arrow in the tool bar:
+
+:::image type="content" source="media/use-the-ssms-xe-profiler/start-feed.png" alt-text="Screenshot of the start data feed option in the extended events menu in SSMS.":::
+
+Likewise, after a session is started, to stop a session select **Stop data feed** from the **Extended Events** menu in the Live Data Viewer or use the red square in the tool bar.
 
-3. In Object Explorer, find the XE Profiler menu item and expand it by clicking the '+' sign.
+## Customize the session
 
-   ![XEProfiler Menu](media/xevents-xe-profiler-menu.png)
+While XEvent Profiler provides the preconfigured **Standard** and **T-SQL** sessions, you can further customize the session to meet your needs by doing the following:
 
-4. Double-click **Standard** if you want to view all events in this session. Click **T-SQL** if you want to view the logged SQL statements. If a session is not already created, a session is created for you.
+- **Add or remove columns**: Right-click on any column header in the Live Data viewer and select **Choose Columns...** to add or remove columns to control the display of additional information.
+- **Filter events**: Right-click on any field in the Live Data viewer and select **Filter by this value** to apply criteria to the captured events, such as to focus on a specific application, user, or event type. Alternatively, you can select **Filters...** from the top navigation bar to open the filter dialog box.
 
-   ![XEProfiler Session](media/xevents-xe-profiler-start-session.png)
+## Export data
 
-5. You can now view events captured by the session.
+To save the data for later analysis, you can export the data feed to a table, or either an `XEL` or `CSV` file. To export the feed, select **Export data...** from the **Extended Events** menu.
 
-   ![XEProfiler Viewer](media/xevents-xe-profiler-start-viewer.png)
+## Related content
 
-## See Also
-[Extended Events](../../relational-databases/extended-events/extended-events.md)  
-[Extended Events Tools](../../relational-databases/extended-events/extended-events-tools.md)  
-  
+- [Extended Events overview](extended-events.md)
+- [Extended Events Tools](extended-events-tools.md)

…vents/media/xevents-xe-profiler-menu.png …xe-profiler/xevents-xe-profiler-menu.pngdocs/relational-databases/extended-events/media/xevents-xe-profiler-menu.png renamed to docs/relational-databases/extended-events/media/use-the-ssms-xe-profiler/xevents-xe-profiler-menu.png docs/relational-databases/extended-events/media/xevents-xe-profiler-menu.png renamed to docs/relational-databases/extended-events/media/use-the-ssms-xe-profiler/xevents-xe-profiler-menu.png

@@ -22,7 +22,7 @@ dev_langs:
 ---
 # sys.sp_cdc_help_change_data_capture (Transact-SQL)
 
-[!INCLUDE [SQL Server](../../includes/applies-to-version/sqlserver.md)]
+[!INCLUDE [SQL Server](../../includes/applies-to-version/sql-asdbmi.md)]
 
 Returns the change data capture configuration for each table enabled for change data capture in the current database. Up to two rows can be returned for each source table, one row for each capture instance. Change data capture isn't available in every edition of [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)]. For a list of features that are supported by the editions of [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)], see [Editions and supported features of SQL Server 2022](../../sql-server/editions-and-components-of-sql-server-2022.md).
 

…ia/xevents-xe-profiler-start-session.png …er/xevents-xe-profiler-start-session.pngdocs/relational-databases/extended-events/media/xevents-xe-profiler-start-session.png renamed to docs/relational-databases/extended-events/media/use-the-ssms-xe-profiler/xevents-xe-profiler-start-session.png docs/relational-databases/extended-events/media/xevents-xe-profiler-start-session.png renamed to docs/relational-databases/extended-events/media/use-the-ssms-xe-profiler/xevents-xe-profiler-start-session.png

@@ -128,7 +128,6 @@ To delete the resources from Azure portal:
 1. Select **Delete resource group**.
 1. Confirm the resource group name at **Type the resource group name**, and select Delete.
 
-[!INCLUDE [manage-extension](includes/manage-extension.md)]
 
 ## Related content