Merge pull request #35272 from MicrosoftDocs/main

09/10/2025 PM Publish

Author: Albertyang0

azure-sql/database/sql-data-sync-data-sql-server-sql-database.md

@@ -237,6 +237,7 @@ Yes. You can configure sync between databases that belong to resource groups own
 
 - If the subscriptions belong to the same tenant and you have permission to all subscriptions, you can configure the sync group in the Azure portal.
 - Otherwise, you have to use PowerShell to add the sync members.
+- Private Link is not supported in cross-tenant scenarios.
 
 ### Can I set up Data Sync to sync between databases in SQL Database that belong to different clouds (like Azure Public Cloud and Azure operated by 21Vianet)?
 

docs/includes/applies-to-version/sql-asdb-asdbmi-asa-dedicated-poolonly-fabricsqldb-fabricdw.md

@@ -0,0 +1,9 @@
+---
+author: WilliamDAssafMSFT
+ms.author: wiassaf
+ms.date: 09/08/2025
+ms.service: sql
+ms.topic: include
+---
+
+[!INCLUDE [Applies to](../../includes/applies-md.md)] [!INCLUDE [SQL Server](_ssnoversion.md)] [!INCLUDE [Azure SQL Database](../../includes/applies-to-version/_asdb.md)] [!INCLUDE [SQL Managed Instance](../../includes/applies-to-version/_asmi.md)] [!INCLUDE [Azure Synapse Analytics (dedicated SQL pool only)](../../includes/applies-to-version/_asa-sqlpool-only.md)] [!INCLUDE [fabric-sqldb](_fabric-sqldb.md)] [!INCLUDE [Fabric Data Warehouse](../../includes/applies-to-version/_fabric-dw.md)]

docs/relational-databases/system-functions/sys-fn-msxe-read-event-stream-transact-sql.md

@@ -3,7 +3,8 @@ title: "sys.fn_MSxe_read_event_stream (Transact-SQL)"
 description: "sys.fn_MSxe_read_event_stream (Transact-SQL)"
 author: rwestMSFT
 ms.author: randolphwest
-ms.date: "06/10/2016"
+ms.reviewer: dfurman
+ms.date: 09/10/2025
 ms.service: sql
 ms.subservice: system-objects
 ms.topic: "reference"
@@ -18,41 +19,57 @@ helpviewer_keywords:
 dev_langs:
   - "TSQL"
 ---
+
 # sys.fn_MSxe_read_event_stream (Transact-SQL)
-[!INCLUDE [SQL Server](../../includes/applies-to-version/sqlserver.md)]
-
-  Extended Events provides a table valued function (TVF) for internal use by the Extended Events user interface (UI). The table does not provide customer usable data.  
-  
- To view event data, use one of the following:  
-  
--   Extended Events New Session UI.  
-  
--   fn_xe_file_target_read_file TVF. For more information, see [sys.fn_xe_file_target_read_file (Transact-SQL)](../../relational-databases/system-functions/sys-fn-xe-file-target-read-file-transact-sql.md).  
-  
-  
- :::image type="icon" source="../../includes/media/topic-link-icon.svg" border="false"::: [Transact-SQL syntax conventions](../../t-sql/language-elements/transact-sql-syntax-conventions-transact-sql.md)  
-  
-## Syntax  
-  
-```  
-  
-sys.fn_MSxe_read_event_stream ( session_name)  
-```  
-  
-## Arguments  
- *Session_name*  
- The name of a session that is running on the server.  
-  
-## Table Returned  
-  
-|Column name|Data type|Description|  
-|-----------------|---------------|-----------------|  
-|type|**Integer (4)**|The event type. Is not nullable.|  
-|data|**Image (16)**|The event image data. Is nullable.|  
-  
-## See Also  
- [Extended Events Dynamic Management Views](../../relational-databases/system-dynamic-management-views/extended-events-dynamic-management-views.md)   
- [Extended Events Catalog Views (Transact-SQL)](../../relational-databases/system-catalog-views/extended-events-catalog-views-transact-sql.md)   
- [Extended Events](../../relational-databases/extended-events/extended-events.md)  
-  
-  
+
+[!INCLUDE [SQL Server SQL Database SQL Managed Instance](../../includes/applies-to-version/sql-asdb-asdbmi.md)]
+
+`sys.fn_MSxe_read_event_stream` returns binary data for internal use by the [QueryableXEventData](/dotnet/api/microsoft.sqlserver.xevent.linq.queryablexeventdata) .NET class. Extended Events UI in the [!INCLUDE [ssManStudioFull](../../includes/ssmanstudiofull-md.md)] (SSMS) uses this class to read event session data.
+
+To view human-readable event data, use one of the following instead of calling `sys.fn_MSxe_read_event_stream` directly:
+
+- Extended Events UI in SSMS.
+- [sys.fn_xe_file_target_read_file](sys-fn-xe-file-target-read-file-transact-sql.md) table-valued function.
+
+:::image type="icon" source="../../includes/media/topic-link-icon.svg" border="false"::: [Transact-SQL syntax conventions](../../t-sql/language-elements/transact-sql-syntax-conventions-transact-sql.md)
+
+## Syntax
+
+```syntaxsql
+sys.fn_MSxe_read_event_stream ( source , source_option )
+```
+
+## Arguments
+
+#### *source*
+
+The specific source of event data returned by the function. *Source* is **nvarchar(260)** with no default.
+
+*Source* is interpreted differently depending on the value of *source_option*:
+
+| *source_option* | Interpretation of *source* |
+| --- | --- |
+| `0` | *Source* is the name of a started event session. |
+| `1` | *Source* is the path to the event session log files to read.<br /><br />When used with files in the local file system, *source* must include the name of an event session log file and can contain `*` as a wildcard.<br /><br />When used with blobs in an Azure Storage container, *source* is an HTTP URL constructed by the concatenation of two parts:<br /><br />1. The path to an Azure Storage storage container, followed by a slash (`/`).<br />2. A common prefix for the names of blobs in the container that should be read.<br /><br />For example, using `https://<storage-account-name>.blob.core.windows.net/container-name>/xe_session` as *source* retrieves data from all blobs with names starting with `xe_session`, and regardless of the remainder of the blob name including the extension. Wildcards can't be specified. A credential allowing access to the Azure Storage container must exist. |
+
+#### *source_option*
+
+The option that determines the type of the event data source. Possible values are:
+
+| Value | Description |
+| --- | --- |
+| `0` | Returns event data from the [event_stream](../extended-events/targets-for-extended-events-in-sql-server.md#event_stream-target) target of a started event session. The function executes indefinitely, returning new event data as the session produces it. |
+| `1` | Returns event data from the extended event log files specified by *source*. |
+
+## Table returned
+
+| Column name | Data type | Description |
+| --- | --- | --- |
+| type | **int** | The event type. Not nullable. |
+| data | **image** | Binary event data. Is nullable. |
+
+## Related content
+
+- [Extended Events Dynamic Management Views](../system-dynamic-management-views/extended-events-dynamic-management-views.md)
+- [Extended Events Catalog Views (Transact-SQL)](../system-catalog-views/extended-events-catalog-views-transact-sql.md)
+- [Extended Events overview](../extended-events/extended-events.md)

docs/relational-databases/system-functions/sys-fn-xe-file-target-read-file-transact-sql.md

@@ -3,7 +3,8 @@ title: "sys.fn_xe_file_target_read_file (Transact-SQL)"
 description: "The sys.fn_xe_file_target_read_file system function reads files created by the Extended Events asynchronous file target."
 author: rwestMSFT
 ms.author: randolphwest
-ms.date: 10/10/2024
+ms.reviewer: dfurman
+ms.date: 09/10/2025
 ms.service: sql
 ms.subservice: system-objects
 ms.topic: "reference"
@@ -20,13 +21,14 @@ dev_langs:
   - "TSQL"
 monikerRange: "=azuresqldb-current || >=sql-server-2016 || >=sql-server-linux-2017 || =azuresqldb-mi-current"
 ---
+
 # sys.fn_xe_file_target_read_file (Transact-SQL)
 
 [!INCLUDE [SQL Server SQL Database SQL Managed Instance](../../includes/applies-to-version/sql-asdb-asdbmi.md)]
 
-Reads files created by the Extended Events asynchronous file target. One event, in XML format, is returned per row.
+Reads the event log XEL files created by the Extended Events `event_file` target. Each row in the result set represents an event. Event data is returned in XML format.
 
-The Extended Events `event_file` target stores the data it receives in a binary format that isn't human readable. Read the contents of the `.xel` file with the `sys.fn_xe_file_target_read_file` function. These files can also be read from [!INCLUDE [ssManStudio](../../includes/ssmanstudio-md.md)]. For a walkthrough, see [Quickstart: Extended Events](../extended-events/quick-start-extended-events-in-sql-server.md).
+XEL files can also be read by [!INCLUDE [ssManStudioFull](../../includes/ssmanstudiofull-md.md)]. For a walkthrough, see [Quickstart: Extended Events](../extended-events/quick-start-extended-events-in-sql-server.md).
 
 :::image type="icon" source="../../includes/media/topic-link-icon.svg" border="false"::: [Transact-SQL syntax conventions](../../t-sql/language-elements/transact-sql-syntax-conventions-transact-sql.md)
 
@@ -40,24 +42,36 @@ sys.fn_xe_file_target_read_file ( path , mdpath , initial_file_name , initial_of
 
 #### *path*
 
-The path to the files to read. *path* can contain wildcards and include the name of a file. *path* is **nvarchar(260)** with no default. In the context of Azure SQL Database, this value is an HTTP URL to a file in Azure Storage.
+The path to the files to read. *path* is **nvarchar(260)** with no default.
+
+- When used with files in the local file system, *path* must include the name of an event session log file. The file name can contain `*` as a wildcard to read data from multiple files.
+
+- When used with blobs in an Azure Storage container, *path* is an HTTP URL constructed by the concatenation of two parts:
+
+  1. The path to an Azure Storage storage container, followed by a slash (`/`).
+
+  1. A common prefix for the names of blobs in the container that should be read. To read a single blob, use the full name of the blob.
+
+  For example, using `https://<storage-account-name>.blob.core.windows.net/container-name>/xe_session` as *path* retrieves data from all blobs with names starting with `xe_session`, and regardless of the remainder of the blob name including the extension. Wildcards can't be specified.
 
 #### *mdpath*
 
 The path to the metadata file that corresponds to the file or files specified by the *path* argument. *mdpath* is **nvarchar(260)** with no default.
 
-In [!INCLUDE [sssql11-md](../../includes/sssql11-md.md)] and later versions, you don't need this parameter. It was retained for backward compatibility, for log files generated in previous versions of SQL Server. In [!INCLUDE [sssql16-md](../../includes/sssql16-md.md)] and later versions, this parameter can be given as `NULL`, as `.xem` files are no longer used.
+In [!INCLUDE [sssql11-md](../../includes/sssql11-md.md)] and later versions, you don't need this parameter. It's retained for backward compatibility, for log files generated in previous versions of SQL Server. In [!INCLUDE [sssql16-md](../../includes/sssql16-md.md)] and later versions, this parameter can be given as `NULL`, as `.xem` files are no longer used.
 
 #### *initial_file_name*
 
 The first file to read from *path*. *initial_file_name* is **nvarchar(260)** with no default. If `NULL` is specified as the argument, all the files found in *path* are read.
 
-> [!NOTE]  
-> *initial_file_name* and *initial_offset* are paired arguments. If you specify a value for either argument, you must specify a value for the other argument.
+The file name must be a value returned in the result set of a `sys.fn_xe_file_target_read_file` function call with the same *path*.
 
 #### *initial_offset*
 
-Used to specify last offset read previously and skips all events up to the offset (inclusive). Event enumeration starts after the offset specified. *initial_offset* is **bigint**. If `NULL` is specified as the argument, the entire file is read.
+Used to specify last offset read previously. Skips all events up to the offset (inclusive). Event enumeration starts after the offset specified. *initial_offset* is **bigint**. If `NULL` is specified as the argument, the entire file is read.
+
+> [!NOTE]  
+> *initial_file_name* and *initial_offset* are paired arguments. If you specify a value for either argument, you must specify a value for the other argument.
 
 ## Table returned
 
@@ -69,7 +83,7 @@ Used to specify last offset read previously and skips all events up to the offse
 | `event_data` | **nvarchar(max)** | The event contents, in XML format. Not nullable. |
 | `file_name` | **nvarchar(260)** | The name of the file that contains the event. Not nullable. |
 | `file_offset` | **bigint** | The offset of the block in the file that contains the event. Not nullable. |
-| `timestamp_utc` | **datetime2(7)** | The date and time (UTC timezone) of the event. Not nullable.<br /><br />**Applies to**: [!INCLUDE [sssql17](../../includes/sssql17-md.md)] and later versions, and [!INCLUDE [ssazure-sqldb](../../includes/ssazure-sqldb.md)]. |
+| `timestamp_utc` | **datetime2(7)** | The date and time (UTC timezone) of the event. Not nullable.<br /><br />**Applies to**: [!INCLUDE [sssql17](../../includes/sssql17-md.md)] and later versions, [!INCLUDE [ssazure-sqldb](../../includes/ssazure-sqldb.md)], and [!INCLUDE [ssazuremi-md](../../includes/ssazuremi-md.md)]. |
 
 ## Remarks
 
@@ -79,9 +93,11 @@ Reading large result sets by executing `sys.fn_xe_file_target_read_file` in [!IN
 
 ### Azure SQL
 
-In [!INCLUDE [ssazuremi-md](../../includes/ssazuremi-md.md)] or [!INCLUDE [ssazure-sqldb](../../includes/ssazure-sqldb.md)], store `.xel` files in Azure Blob Storage. You can use `sys.fn_xe_file_target_read_file` to read from extended event sessions you create yourself and store in Azure Blob Storage. For example walkthrough, review [Create an event session with an event_file target in Azure Storage](/azure/azure-sql/database/xevent-code-event-file).
+In [!INCLUDE [ssazuremi-md](../../includes/ssazuremi-md.md)] or [!INCLUDE [ssazure-sqldb](../../includes/ssazure-sqldb.md)], the files created by the `event_file` target are always stored as blobs in an Azure Storage container.
 
-If you specify wildcard and/or a path for a local file system, you receive an error message similar to:
+You can use `sys.fn_xe_file_target_read_file` to read data from these blobs if a credential allowing access to the Azure Storage container exists. For a walkthrough, review [Create an event session with an event_file target in Azure Storage](/azure/azure-sql/database/xevent-code-event-file).
+
+If you specify a local file system path, you receive an error message similar to:
 
 ```output
 Msg 40538, Level 16, State 3, Line 15
@@ -96,7 +112,7 @@ In [!INCLUDE [sssql22-md](../../includes/sssql22-md.md)] and later versions, req
 
 ## Examples
 
-### A. Retrieve data from file targets
+### A. Retrieve data from files in the local file system
 
 For [!INCLUDE [ssSQL14](../../includes/sssql14-md.md)] and previous versions, the following example gets all the rows from all the files, including both the `.xel` and `.xem` file. In this example, the file targets and metafiles are located in the trace folder in the `C:\traces\` folder.
 
@@ -117,7 +133,45 @@ In [!INCLUDE [sssql17](../../includes/sssql17-md.md)] and later versions, the fo
 ```sql
 SELECT *
 FROM sys.fn_xe_file_target_read_file('system_health*.xel', NULL, NULL, NULL)
-WHERE CAST(timestamp_utc AS DATETIME2(7)) > DATEADD(DAY, -1, GETUTCDATE());
+WHERE CAST (timestamp_utc AS DATETIME2 (7)) > DATEADD(DAY, -1, GETUTCDATE());
+```
+
+### B. Retrieve data from blobs in an Azure Storage container
+
+Read data from all blobs in the container with names starting with `xe_session_`.
+
+```sql
+SELECT *
+FROM sys.fn_xe_file_target_read_file(
+    'https://<storage-account-name>.blob.core.windows.net/<container-name>/xe_session_',
+    NULL,
+    NULL,
+    NULL
+);
+```
+
+Read data from the `xe_session_0_133614763336380000.xel` blob.
+
+```sql
+SELECT *
+FROM sys.fn_xe_file_target_read_file(
+    'https://<storage-account-name>.blob.core.windows.net/<container-name>/xe_session_0_133614763336380000.xel',
+    NULL,
+    NULL,
+    NULL
+);
+```
+
+Read data from the `xe_session_0_133614763336380000.xel` blob starting with offset 33280.
+
+```sql
+SELECT *
+FROM sys.fn_xe_file_target_read_file(
+    'https://<storage-account-name>.blob.core.windows.net/<container-name>/xe_session_',
+    NULL,
+    'https://<storage-account-name>.blob.core.windows.net/<container-name>/xe_session_0_133614763336380000.xel',
+    33280
+);
 ```
 
 ## Related content

docs/ssdt/alter-dacfx-used-by-ssdt.md

@@ -1,10 +1,10 @@
 ---
-title: Alter DacFx used by SQL Server Data Tools (SSDT)
+title: "Alter DacFx Used by SQL Server Data Tools (SSDT)"
 description: "Learn how to manually change the DacFx version used by SQL Server Data Tools (SSDT)."
 author: dzsquared
 ms.author: drskwier
-ms.reviewer: maghan
-ms.date: 03/15/2024
+ms.reviewer: randolphwest
+ms.date: 09/09/2025
 ms.service: sql
 ms.subservice: ssdt
 ms.topic: how-to
@@ -16,7 +16,7 @@ monikerRange: ">=aps-pdw-2016 || =azuresqldb-current || =azure-sqldw-latest || >
 
 # Alter DacFx used by SQL Server Data Tools (SSDT)
 
-Under specific circumstances you might need to use a different version of [DacFx](../tools/sqlpackage/sqlpackage.md) with the SQL Server Data Tools interface in Visual Studio. When possible, it is recommended to use a standalone version of DacFx if an alternative version from SQL Server Data Tools is required.
+Under specific circumstances you might need to use a different version of [DacFx](../tools/sqlpackage/sqlpackage.md) with the SQL Server Data Tools interface in Visual Studio. When possible, it's recommended to use a standalone version of DacFx if an alternative version from SQL Server Data Tools is required.
 
 Follow the process below to alter the version of DacFx used by SQL Server Data Tools (SSDT).
 
@@ -42,9 +42,9 @@ DacFx is published to [NuGet](https://www.nuget.org/packages/Microsoft.SqlServer
    - Microsoft.SqlServer.TransactSql.ScriptDom.dll
    - Microsoft.SqlServer.Types.dll
 
-SQL Projects will require [Clean or Rebuild](/visualstudio/ide/building-and-cleaning-projects-and-solutions-in-visual-studio) after this process to properly incorporate the replaced DacFx version.
+SQL Projects require [Clean or Rebuild](/visualstudio/ide/building-and-cleaning-projects-and-solutions-in-visual-studio) after this process to properly incorporate the replaced DacFx version.
 
 ## Related content
 
-- [SQL Server Data Tools (SSDT) overview](sql-server-data-tools.md)
-- [SqlPackage.exe (DacFx) release notes](../tools/sqlpackage/release-notes-sqlpackage.md)
+- [SQL Server Data Tools](sql-server-data-tools.md)
+- [Release notes for SqlPackage](../tools/sqlpackage/release-notes-sqlpackage.md)