Merge pull request #34707 from MicrosoftDocs/main

Auto Publish – main to live - 2025-07-15 22:30 UTC

Author: learn-build-service-prod[bot]

docs/linux/sql-server-linux-polybase.md

@@ -4,7 +4,7 @@ description: Learn how to connect to ODBC data sources with PolyBase on SQL Serv
 author: HugoMSFT
 ms.author: hudequei
 ms.reviewer: mikeray, randolphwest
-ms.date: 06/11/2025
+ms.date: 07/15/2025
 ms.service: sql
 ms.subservice: linux
 ms.topic: conceptual
@@ -153,30 +153,6 @@ Failed to bind port "127.0.0.1:25100"
 
 You can find this message in PolyBase's log file, located at: `/var/opt/mssql-polybase-ees/log/`. In [!INCLUDE [sssql25-md](../includes/sssql25-md.md)] and later versions, the location has moved to `/var/opt/mssql/log/polybase-ees-log`.
 
-To fix, customize the service to use an available port and restart.
-
-1. Find and edit the `/var/opt/mssql/binn/PolyBase/DMs.exe.config` file. Locate the key entry `EESPort`, and assign the new port.
-
-1. Find and edit the `/var/opt/mssql/binn/PolyBase/DWEngineService.exe.config` file. Locate the key entry `EESPort`, and assign the new port.
-
-1. Run the following command to restart the service informing the new port:
-
-   ```bash
-   sudo /opt/mssql/lib/dotnet6/dotnet/opt/mssql/lib/ExternalExecutionService.dll -port <newportnumber>
-   ```
-
-   In [!INCLUDE [sssql25-md](../includes/sssql25-md.md)] and later versions, use the following command instead:
-
-   ```bash
-   sudo /opt/mssql/bin/mssql-conf set polybaseEES eesport <newportnumber>
-   ```
-
-1. You're prompted to restart the PolyBase service.
-
-   ```bash
-   systemctl restart mssql-ees.service
-   ```
-
 ## Related content
 
 - [Install PolyBase on Linux](../relational-databases/polybase/polybase-linux-setup.md)

docs/sql-server/azure-arc/manage-autodeploy.md

@@ -27,7 +27,9 @@ Complete the [Prerequisites - SQL Server enabled by Azure Arc](prerequisites.md)
 
 Optionally, specify the license type for each instance of SQL Server.
 
-To specify the desired license type, provide the license type value tag. The automatic connecting workflow requires that tag. For more information, visit [Tag resources, resource groups, and subscriptions for a logical organization](/azure/azure-resource-manager/management/tag-resources).
+To specify the desired license type, provide the license type value tag. The automatic connecting workflow requires that tag. For more information, visit [Tag resources, resource groups, and subscriptions for a logical organization](/azure/azure-resource-manager/management/tag-resources). 
+
+You can set tag values at the subscription, resource group, or resource level. Tag values set at subscription level supersede values set at the resource group and resource level. Tag values set at the resource group level supersede values set at the resource level.
 
 Add one of the following tags and values to your subscription, resource groups, or Arc Server resources.
 
@@ -42,6 +44,8 @@ Microsoft uses this value when the automatic connecting workflow deploys the SQL
 > [!IMPORTANT]  
 > To maximize the value of Azure Arc for SQL Server customers, Microsoft uses an automated process of determining the license type value if you haven't set the default value using the `ArcSQLServerExtensionDeployment` tag. If your SQL Server is covered by Software Assurance (SA) or Subscription and Support, and the number of licenses you have purchased is greater than the number of licenses you already committed to Azure to use Azure Hybrid Benefit, this process sets the license type value to **Paid** for the onboarded SQL Server instances on a first-come-first-serve basis. As a result, you automatically have access to valuable management features provided to SA customers.
 
+### License type setting precedence
+
 ## Automatically install the Azure Extension for SQL Server on new servers connected to Arc
 
 Microsoft automatically installs Azure extension for SQL Server on each Arc-enabled server connected to Azure Arc if it has any installed SQL Server instances. This automated process involves the following tasks:

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

@@ -12,6 +12,7 @@ dev_langs:
   - "TSQL"
 monikerRange: "=azuresqldb-mi-current || >=sql-server-2016 || =azuresqldb-current || >=sql-server-linux-2017 || =fabric"
 ---
+
 # OPENROWSET BULK (Transact-SQL)
 
 ::: moniker range="=azuresqldb-mi-current||=azuresqldb-current||>=sql-server-2016||>=sql-server-linux-2017"
@@ -281,7 +282,21 @@ To bulk export or import SQLXML data, use one of the following data types in you
 
 ## Permissions
 
-`OPENROWSET` permissions are determined by the permissions of the user name that is being passed to the data provider. To use the `BULK` option requires `ADMINISTER BULK OPERATIONS` or `ADMINISTER DATABASE BULK OPERATIONS` permission.
+`OPENROWSET` with external data sources, requires the following permissions:
+
+- `ADMINISTER DATABASE BULK OPERATIONS`
+
+  or
+
+- `ADMINISTER BULK OPERATIONS`
+
+The following example grants `ADMINISTEER DATABASE BULK OPERATIONS` to a principal.
+
+```sql
+GRANT ADMINISTER DATABASE BULK OPERATIONS TO [<principal_name>];
+```
+
+If the target storage account is private, the principal must also have the **Storage Blob Data Reader** role (or higher) assigned at the container or storage account level.
 
 ## Examples