Merge branch 'main' of https://github.com/MicrosoftDocs/sql-docs-pr into HugoMSFT-docs-editor/dbcc-traceon-trace-flags-trans-1753801646

Author: WilliamDAssafMSFT

azure-sql/toc.yml

@@ -1917,8 +1917,10 @@
   - name: Feature availability by region
     items: 
     - name: Azure SQL Database
+      displayName: Feature availability by region Azure SQL Database
       href: database/region-availability.md
     - name: Azure SQL Managed Instance
+      displayName: Feature availability by region Azure SQL Managed Instance
       href: managed-instance/region-availability.md
   - name: Monitoring data reference 
     items:  

docs/reporting-services/reporting-services-consolidation-faq.md

@@ -55,9 +55,9 @@ PBIRS is a superset of SSRS, offering all SSRS capabilities plus support for int
 
 PBIRS will be available for all paid editions of [!INCLUDE [ssnoversion-md](../includes/ssnoversion-md.md)], including licenses with no Software Assurance (SA). You can expect more information about specific [!INCLUDE [ssnoversion-md](../includes/ssnoversion-md.md)] editions when SQL Server 2025 is in General Availability (GA). In the meantime, you can explore PBIRS by installing one of the [free Developer or Evaluation](/power-bi/report-server/install-report-server) editions.
 
-### Why isn't there an SSRS equivalent for non-SA customers?
+### Is there an SSRS equivalent for non-SA customers going forward?
 
-PBIRS will be available for all paid editions of [!INCLUDE [ssnoversion-md](../includes/ssnoversion-md.md)], including licenses with no Software Assurance (SA).
+PBIRS will be available for all paid editions of [!INCLUDE [ssnoversion-md](../includes/ssnoversion-md.md)] regardless of licensing programs. For instance, license-only customers and SPLA customers who run paid editions have access to Power BI Report Server without incurring additional costs, same as customers with Software Assurance.
 
 ### How long can customers use their existing SSRS installations?
 

docs/t-sql/functions/opendatasource-transact-sql.md

@@ -36,14 +36,16 @@ OPENDATASOURCE ( 'provider_name', 'init_string' )
 
 ## Arguments
 
-#### '*provider_name*'  
- Is the name registered as the PROGID of the OLE DB provider used to access the data source. *provider_name* is a **char** data type, with no default value.  
+#### '*provider_name*'
+
+The name registered as the PROGID of the OLE DB provider used to access the data source. *provider_name* is a **char** data type, with no default value.  
 
  > [!IMPORTANT]
  > [!INCLUDE[snac-removed-oledb-only](../../includes/snac-removed-oledb-only.md)]
 
- #### '*init_string*'  
- Is the connection string passed to the IDataInitialize interface of the destination provider. The provider string syntax is based on keyword-value pairs separated by semicolons, such as: **'**_keyword1_=_value_ **;** _keyword2_=_value_**'**.  
+#### '*init_string*'
+
+The connection string passed to the IDataInitialize interface of the destination provider. The provider string syntax is based on keyword-value pairs separated by semicolons, such as: `'keyword1=value;keyword2=value'`.  
 
  For specific keyword-value pairs supported on the provider, see the [!INCLUDE[msCoName](../../includes/msconame-md.md)] Data Access SDK. This documentation defines the basic syntax. The following table lists the most frequently used keywords in the *init_string* argument.  
 
@@ -63,7 +65,7 @@ OPENDATASOURCE ( 'provider_name', 'init_string' )
 
 `OPENDATASOURCE` can be used to access remote data from OLE DB data sources only when the DisallowAdhocAccess registry option is explicitly set to 0 for the specified provider, and the Ad Hoc Distributed Queries advanced configuration option is enabled. When these options are not set, the default behavior does not allow for ad hoc access.  
 
-The `OPENDATASOURCE` function can be used in the same [!INCLUDE[tsql](../../includes/tsql-md.md)] syntax locations as a linked-server name. Therefore, `OPENDATASOURCE` can be used as the first part of a four-part name that refers to a table or view name in a SELECT, INSERT, UPDATE, or DELETE statement, or to a remote stored procedure in an EXECUTE statement. When executing remote stored procedures, `OPENDATASOURCE` should refer to another instance of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)]. OPENDATASOURCE does not accept variables for its arguments.  
+The `OPENDATASOURCE` function can be used in the same [!INCLUDE[tsql](../../includes/tsql-md.md)] syntax locations as a linked-server name. Therefore, `OPENDATASOURCE` can be used as the first part of a four-part name that refers to a table or view name in a SELECT, INSERT, UPDATE, or DELETE statement, or to a remote stored procedure in an EXECUTE statement. In remote stored procedures, `OPENDATASOURCE` should refer to another instance of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)]. OPENDATASOURCE does not accept variables for its arguments.  
 
 Like the `OPENROWSET` function, `OPENDATASOURCE` should only reference OLE DB data sources that are accessed infrequently. Define a linked server for any data sources accessed more than several times. Neither OPENDATASOURCE nor OPENROWSET provides all the functionality of linked-server definitions, such as security management and the ability to query catalog information. All connection information, including passwords, must be provided every time that OPENDATASOURCE is called.  
 
@@ -72,11 +74,15 @@ Like the `OPENROWSET` function, `OPENDATASOURCE` should only reference OLE DB da
   
 The connection requirements for each provider are similar to the requirements for those parameters when creating linked servers. The details for many common providers are listed in the article [sp_addlinkedserver (Transact-SQL)](../../relational-databases/system-stored-procedures/sp-addlinkedserver-transact-sql.md).  
 
-Any call to `OPENDATASOURCE`, `OPENQUERY`, or `OPENROWSET` in the `FROM` clause is evaluated separately and independently from any call to these functions used as the target of the update, even if identical arguments are supplied to the two calls. In particular, filter or join conditions applied on the result of one of those calls has no effect on the results of the other.  
-  
+Any call to `OPENDATASOURCE`, `OPENQUERY`, or `OPENROWSET` in the `FROM` clause is evaluated separately and independently from any call to these functions used as the target of the update, even if identical arguments are supplied to the two calls. In particular, filter or join conditions applied on the result of one of those calls has no effect on the results of the other. 
+
 ## Permissions  
  Any user can execute OPENDATASOURCE. The permissions that are used to connect to the remote server are determined from the connection string.  
-  
+
+## Limitations
+
+Not supported with [Microsoft Access Database Engine driver](https://support.microsoft.com/office/download-and-install-microsoft-365-access-runtime-185c5a32-8ba9-491e-ac76-91cbe3ea09c9). 
+ 
 ## Examples  
 
 ### A. Using OPENDATASOURCE with SELECT and the SQL Server OLE DB Driver  

docs/t-sql/functions/openrowset-transact-sql.md

@@ -151,6 +151,10 @@ Any call to `OPENDATASOURCE`, `OPENQUERY`, or `OPENROWSET` in the `FROM` clause
 
 `OPENROWSET` permissions are determined by the permissions of the user name that is being passed to the data provider.
 
+## Limitations
+
+Not supported with [Microsoft Access Database Engine driver](https://support.microsoft.com/office/download-and-install-microsoft-365-access-runtime-185c5a32-8ba9-491e-ac76-91cbe3ea09c9). 
+
 ## Examples
 
 This section provides general examples to demonstrate how to use OPENROWSET.