Merge pull request #36114 from MicrosoftDocs/main

Auto Publish – main to live - 2025-12-18 18:30 UTC

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

.openpublishing.redirection.ssms.json

@@ -6189,6 +6189,11 @@
       "source_path": "docs/ssms/visual-db-tools/work-with-tables-in-database-diagram-visual-database-tools.md",
       "redirect_url": "/ssms/visual-db-tools/work-with-tables-in-database-diagram-visual-database-tools",
       "redirect_document_id": false
+    },
+    {
+      "source_path": "docs/tools/sqlcmd/edit-sqlcmd-scripts-query-editor.md",
+      "redirect_url": "/ssms/scripting/sqlcmd-scripts-query-editor",
+      "redirect_document_id": false
     }
   ]
 }

azure-sql/virtual-machines/windows/sql-assessment-for-sql-vm.md

@@ -256,6 +256,18 @@ After a VM is associated with a Log Analytics workspace, it can't be changed fro
 
 This error indicates that results are no longer retained in the Log Analytics workspace, based on its retention policy. You can [change the retention period](/azure/azure-monitor/logs/manage-cost-storage#change-the-data-retention-period) for the workspace.
 
+### SQL best practice assessment not enabled in Azure portal after enabling via Azure Policy or other automation
+
+The names of the data collection rule and data collection rule association for **SQL best practice assessment** follow a specific *case-sensitive* naming convention. If **SQL best practice assessment** is enabled by using an Azure Policy, or some other form of automation, which creates a name that fails to follow the appropriate naming convention, **SQL best practices assessment** won't be enabled. 
+
+Both the data collection rule and data collection rule association names are *case sensitive*, with `DCR` and `DCRA` capitalized, while the rest of the name must be lower case.
+
+The names must use the following naming conventions:
+
+- The data collection rule must be named using the `<guid>_<regionname>_DCR_<number>` naming convention, such as the following example: `37e0cae3-c2bd-44f3-85af-975f28b08871_eastus2_DCR_1`
+- The data collection rule association must be named using the `<guid>_<regionname>_DCRA_<number>` naming convention, such as the following example: `37e0cae3-c2bd-44f3-85af-975f28b08871_eastus2_DCRA_1`
+
+
 ## Related content
 
 - [Automatic registration with SQL IaaS Agent extension](sql-agent-extension-automatic-registration-all-vms.md)

docs/database-engine/availability-groups/windows/create-clustered-dtc-for-an-always-on-availability-group.md

@@ -18,7 +18,7 @@ This article walks you through a complete configuration of a clustered DTC resou
 
 The walkthrough creates a clustered DTC resource and the [!INCLUDE [ssnoversion-md](../../../includes/ssnoversion-md.md)] AGs to align with the requirements at [How to cluster the DTC service for an Always On availability group](cluster-dtc-for-sql-server-2016-availability-groups.md).
 
-The walkthrough uses PowerShell and Transact-SQL (T-SQL) scripts. Many of the T-SQL scripts require **SQLCMD Mode** to be enabled. For more information on **SQLCMD Mode**, see [Edit SQLCMD Scripts with Query Editor](../../../tools/sqlcmd/edit-sqlcmd-scripts-query-editor.md). The PowerShell module `FailoverClusters` must be imported. For more information about importing a PowerShell module, see [Importing a PowerShell Module](/powershell/scripting/developer/module/importing-a-powershell-module). This walkthrough is based on the following configuration options:
+The walkthrough uses PowerShell and Transact-SQL (T-SQL) scripts. Many of the T-SQL scripts require **SQLCMD Mode** to be enabled. For more information on **SQLCMD Mode**, see [Edit SQLCMD scripts with Query Editor](/ssms/scripting/sqlcmd-scripts-query-editor). The PowerShell module `FailoverClusters` must be imported. For more information about importing a PowerShell module, see [Importing a PowerShell Module](/powershell/scripting/developer/module/importing-a-powershell-module). This walkthrough is based on the following configuration options:
 
 - All requirements from [Prerequisites, restrictions, and recommendations for Always On availability groups](prereqs-restrictions-recommendations-always-on-availability.md) are met.
 - The domain is `contoso.lab`.

docs/includes/entra-id-tutorial.md

@@ -2,7 +2,7 @@
 author: MikeRayMSFT
 ms.author: mikeray
 ms.reviewer: randolphwest
-ms.date: 07/31/2025
+ms.date: 12/18/2025
 ms.service: sql
 ms.topic: include
 ---
@@ -31,9 +31,13 @@ In this tutorial, you learn how to:
 - Access to Microsoft Entra ID is available for authentication purpose. For more information, see [Microsoft Entra authentication for SQL Server](../relational-databases/security/authentication-access/azure-ad-authentication-sql-server-overview.md).
 - A supported version of [SQL Server Management Studio](/ssms/install/install) is installed on the client machine.
 - A supported certificate.
-- [Network requirements for enabling Entra ID authentication](../sql-server/azure-arc/prerequisites.md#network-requirements-for-enabling-microsoft-entra-authentication)
 
-  Microsoft Entra ID supports CSP certificates. Entra ID doesn't support CNG certificates.
+  > [!WARNING]  
+  > When configuring Microsoft Entra authentication for SQL Server, the certificate used for Microsoft Entra login must have a unique Common Name (CN). If multiple certificates in the computer's certificate store share the same CN, SQL Server might not select the correct certificate for Microsoft Entra authentication, and Microsoft Entra logins will fail.
+
+- [Network requirements for enabling Microsoft Entra ID authentication](../sql-server/azure-arc/prerequisites.md#network-requirements-for-enabling-microsoft-entra-authentication)
+
+  Microsoft Entra ID supports CSP certificates. Microsoft Entra ID doesn't support CNG certificates.
 
 ### Authentication prerequisites
 

docs/relational-databases/replication/concepts/replication-system-stored-procedures-concepts.md

@@ -125,7 +125,7 @@ GO
 ### Creating a SQL Query File in SQL Server Management Studio  
  A replication [!INCLUDE[tsql](../../../includes/tsql-md.md)] script file can be created as a SQL Query file in a [!INCLUDE[ssManStudioFull](../../../includes/ssmanstudiofull-md.md)] project. After the script is written, a connection can be made to the database for this query file and the script can be executed. For more information about how to create [!INCLUDE[tsql](../../../includes/tsql-md.md)] scripts by using [!INCLUDE[ssManStudioFull](../../../includes/ssmanstudiofull-md.md)], see [Query and Text Editors (SQL Server Management Studio)](/ssms/f1-help/database-engine-query-editor-sql-server-management-studio).  
 
- To use a script that includes scripting variables, [!INCLUDE[ssManStudioFull](../../../includes/ssmanstudiofull-md.md)] must be running in **sqlcmd** mode. In **sqlcmd** mode, the Query Editor accepts additional syntax specific to **sqlcmd**, such as `:setvar`, which is used to a value for a variable. For more information about **sqlcmd** mode, see [Edit SQLCMD Scripts with Query Editor](../../../tools/sqlcmd/edit-sqlcmd-scripts-query-editor.md). In the following script, `:setvar` is used to provide a value for the `$(DistPubServer)` variable.  
+ To use a script that includes scripting variables, [!INCLUDE[ssManStudioFull](../../../includes/ssmanstudiofull-md.md)] must be running in SQLCMD mode. In SQLCMD mode, the Query Editor accepts additional syntax specific to **sqlcmd**, such as `:setvar`, which is used to a value for a variable. For more information about SQLCMD mode, see [Edit SQLCMD scripts with Query Editor](/ssms/scripting/sqlcmd-scripts-query-editor). In the following script, `:setvar` is used to provide a value for the `$(DistPubServer)` variable.  
 
 ```  
 :setvar DistPubServer N'MyPublisherAndDistributor';  

docs/relational-databases/security/authentication-access/azure-ad-authentication-sql-server-setup-tutorial.md

@@ -4,7 +4,7 @@ description: Tutorial on how to set up Microsoft Entra authentication for SQL Se
 author: PratimDasgupta
 ms.author: prdasgu
 ms.reviewer: vanto, randolphwest, mikeray
-ms.date: 08/28/2025
+ms.date: 12/18/2025
 ms.service: sql
 ms.subservice: security
 ms.topic: tutorial

docs/sql-server/sql-server-2025-known-issues.md

@@ -4,7 +4,7 @@ description: Known issues, causes, and workarounds for SQL Server 2025 (17.x), c
 author: MikeRayMSFT
 ms.author: mikeray
 ms.reviewer: randolphwest
-ms.date: 11/18/2025
+ms.date: 12/17/2025
 ms.service: sql
 ms.subservice: release-landing
 ms.topic: troubleshooting-known-issue
@@ -19,7 +19,7 @@ monikerRange: ">=sql-server-2016"
 
 This article describes known issues for [!INCLUDE [sssql25-md](../includes/sssql25-md.md)].
 
-[!INCLUDE [sssql25-md](../includes/sssql25-md.md)] has currently identified the following known issues:
+The following issues are currently identified:
 
 - [Installation fails when TLS 1.2 is disabled](#sql-server-2025-installation-fails-when-tls-12-is-disabled)
 - [Windows Arm64 not supported](#windows-arm64-not-supported)
@@ -36,6 +36,7 @@ This article describes known issues for [!INCLUDE [sssql25-md](../includes/sssql
 - [SQL Server audit events don't write to the Security log](#sql-server-audit-events-dont-write-to-the-security-log)
 - [Upgrade fails if Data Quality Services is installed](#upgrade-fails-if-data-quality-services-is-installed)
 - [Full-Text Search fails to index plaintext documents larger than 25 MB](#full-text-search-fails-to-index-plaintext-documents-larger-than-25-mb)
+- [Incorrect license agreement for LocalDB installer](#incorrect-license-agreement-for-localdb-installer)
 
 ## SQL Server 2025 installation fails when TLS 1.2 is disabled
 
@@ -137,13 +138,13 @@ ALTER DATABASE [Database_Name]
     (OPERATION_MODE = READ_WRITE);
 ```
 
-Queries that meet the following conditions could experience an access violation when a PSP [query variant](../relational-databases/performance/parameter-sensitive-plan-optimization.md#query-variant) can't determine the persisted state of its parent dispatcher statement:
+Queries that meet the following conditions might experience an access violation when a PSP [query variant](../relational-databases/performance/parameter-sensitive-plan-optimization.md#query-variant) can't determine the persisted state of its parent dispatcher statement:
 
 - Executed on a secondary replica
 - Sensitive to parameter sniffing
 - Eligible for parameter sensitive plan (PSP) optimization
 
-A fix has been identified and will be part of a future release of [!INCLUDE [sssql25-md](../includes/sssql25-md.md)].
+We have identified a fix for a future release of [!INCLUDE [sssql25-md](../includes/sssql25-md.md)].
 
 **Workaround**: Disable PSP on secondaries for each database that was onboarded to use the Query Store for readable secondaries feature. From within the context of a specific database, issue the following Transact-SQL statement:
 
@@ -154,14 +155,14 @@ ALTER DATABASE SCOPED CONFIGURATION FOR SECONDARY
 
 ## SQL Server audit events don't write to the Security log
 
-Assume that you configured multiple [!INCLUDE [ssnoversion-md](../includes/ssnoversion-md.md)] audit events to write to the Security log in [!INCLUDE [sssql25-md](../includes/sssql25-md.md)]. In this scenario, you notice that all server audits, except the first server audit, don't write. Additionally, when you add the second server audit, you might receive an error that resembles the following message in the [!INCLUDE [ssnoversion-md](../includes/ssnoversion-md.md)] error log:
+Assume that you configured multiple [!INCLUDE [ssnoversion-md](../includes/ssnoversion-md.md)] audit events to write to the [!INCLUDE [sssql25-md](../includes/sssql25-md.md)] Security log. In this scenario, you notice that all server audits, except the first server audit, don't write. Additionally, when you add the second server audit, you might receive an error that resembles the following message in the [!INCLUDE [ssnoversion-md](../includes/ssnoversion-md.md)] error log:
 
 ```output
 Error: 33204, Severity: 17, State: 1.
 SQL Server Audit could not write to the security log.
 ```
 
-A fix has been identified and will be part of a future release of [!INCLUDE [sssql25-md](../includes/sssql25-md.md)].
+We have identified a fix for a future release of [!INCLUDE [sssql25-md](../includes/sssql25-md.md)].
 
 **Workaround**: Use one of the following methods:
 
@@ -226,7 +227,15 @@ Edit the DWORD value `MaxTextFilterBytes`, which is located in `HKEY_LOCAL_MACHI
 reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\ContentIndex" /v MaxTextFilterBytes /t REG_DWORD /d ffffffff
 ```
 
-After updating the registry value, re-issue the Full-Text crawl.
+After updating the registry value, reissue the Full-Text crawl.
+
+## Incorrect license agreement for LocalDB installer
+
+**Issue**: The LocalDB installer points to a preview version of the end-user license agreement (EULA).
+
+To work around this issue, you must download the Express edition installer instead, and choose the **LocalDB** option from the package selection screen.
+
+We have identified a fix for a future release of [!INCLUDE [sssql25-md](../includes/sssql25-md.md)].
 
 ## Related content
 

docs/t-sql/functions/date-bucket-transact-sql.md

@@ -1,10 +1,10 @@
 ---
 title: "DATE_BUCKET (Transact-SQL)"
 description: DATE_BUCKET returns the date-time value corresponding to the start of each date-time bucket from a defined origin timestamp.
-author: kendalvandyke
-ms.author: kendalv
-ms.reviewer: randolphwest
-ms.date: 11/03/2025
+author: rwestMSFT
+ms.author: randolphwest
+ms.reviewer: kendalv, jovanpop
+ms.date: 12/17/2025
 ms.service: sql
 ms.subservice: t-sql
 ms.topic: reference
@@ -18,10 +18,11 @@ helpviewer_keywords:
   - "analytic functions, DATE_BUCKET"
 dev_langs:
   - TSQL
+monikerRange: "=azuresqldb-current || =azuresqldb-mi-current || >=sql-server-ver16 || >=sql-server-linux-ver16 || =fabric || =fabric-sqldb"
 ---
 # DATE_BUCKET (Transact-SQL)
 
-[!INCLUDE [sqlserver2022-asde-fabricsqldb](../../includes/applies-to-version/sqlserver2022-asdb-asmi-asde-fabricsqldb.md)]
+[!INCLUDE [sqlserver2022-asdb-asmi-fabricse-fabricdw-fabricsqldb](../../includes/applies-to-version/sqlserver2022-asdb-asmi-fabricse-fabricdw-fabricsqldb.md)]
 
 This function returns the date-time value corresponding to the start of each date-time bucket from the timestamp defined by the *origin* parameter, or the default origin value of `1900-01-01 00:00:00.000` if the origin parameter isn't specified.
 

docs/toc.yml

@@ -8468,7 +8468,7 @@ items:
     - name: Use with scripting variables
       href: tools/sqlcmd/sqlcmd-use-scripting-variables.md
     - name: Edit SQLCMD scripts with Query Editor
-      href: tools/sqlcmd/edit-sqlcmd-scripts-query-editor.md
+      href: /ssms/scripting/sqlcmd-scripts-query-editor
     - name: Create new local database in a container with sqlcmd
       href: tools/sqlcmd/quickstart-sqlcmd-create-container.md
   - name: SSB Diagnose