Merge pull request #34326 from MicrosoftDocs/main

6/5/2025 PM Publish

Author: Albertyang0

.github/workflows/signoff-review.yml

@@ -3,7 +3,7 @@ title: "Server configuration: max worker threads"
 description: Find out how to use the max worker threads option to configure the number of worker threads that are available to SQL Server to process certain requests.
 author: rwestMSFT
 ms.author: randolphwest
-ms.date: 10/18/2024
+ms.date: 06/05/2024
 ms.service: sql
 ms.subservice: configuration
 ms.topic: conceptual
@@ -74,22 +74,26 @@ The following table shows the automatically configured number of max worker thre
 
 Up to [!INCLUDE [sssql16-md](../../includes/sssql16-md.md)] with Service Pack 1, the *Workers per CPU* only depend on the architecture (32-bit or 64-bit):
 
-| Number of logical CPUs | 32-bit computer <sup>1</sup> | 64-bit computer |
+| Number of logical CPUs | 32-bit computer <sup>&dagger;</sup> | 64-bit computer |
 | --- | --- | --- |
 | \<= 4 | 256 | 512 |
-| \> 4 | 256 + ((logical CPUs - 4) * 8) | 512 <sup>2</sup> + ((logical CPUs - 4) * 16) |
+| \> 4 | 256 + ((logical CPUs - 4) * 8) | 512 <sup>&dagger;&dagger;</sup> + ((logical CPUs - 4) * 16) |
+
+<sup>&dagger;</sup> Starting with [!INCLUDE [sssql16-md](../../includes/sssql16-md.md)], [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] can no longer be installed on a 32-bit operating system. 32-bit computer values are listed for the assistance of customers running [!INCLUDE [ssSQL14](../../includes/sssql14-md.md)] and earlier. We recommend 1,024 as the maximum number of worker threads for an instance of [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] that is running on a 32-bit computer.
+
+<sup>&dagger;&dagger;</sup> Starting with [!INCLUDE [ssSQL17](../../includes/sssql17-md.md)], the *Default Max Workers* value is divided by 2 for machines with less than 2 GB of memory.
 
 Starting with [!INCLUDE [sssql16-md](../../includes/sssql16-md.md)] SP2 and [!INCLUDE [ssSQL17](../../includes/sssql17-md.md)], the *Workers per CPU* depend on the architecture and number of processors (between 4 and 64, or greater than 64):
 
-| Number of logical CPUs | 32-bit computer <sup>1</sup> | 64-bit computer |
+| Number of logical CPUs | 32-bit computer <sup>&dagger;</sup> | 64-bit computer |
 | --- | --- | --- |
 | \<= 4 | 256 | 512 |
-| \> 4 and \<= 64 | 256 + ((logical CPUs - 4) * 8) | 512 <sup>2</sup> + ((logical CPUs - 4) * 16) |
-| \> 64 | 256 + ((logical CPUs - 4) * 32) | 512 <sup>2</sup> + ((logical CPUs - 4) * 32) |
+| \> 4 and \<= 64 | 256 + ((logical CPUs - 4) * 8) | 512 <sup>&dagger;&dagger;</sup> + ((logical CPUs - 4) * 16) |
+| \> 64 | 256 + ((logical CPUs - 4) * 32) | 512 <sup>&dagger;&dagger;</sup> + ((logical CPUs - 4) * 32) |
 
-<sup>1</sup> Starting with [!INCLUDE [sssql16-md](../../includes/sssql16-md.md)], [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] can no longer be installed on a 32-bit operating system. 32-bit computer values are listed for the assistance of customers running [!INCLUDE [ssSQL14](../../includes/sssql14-md.md)] and earlier. We recommend 1,024 as the maximum number of worker threads for an instance of [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] that is running on a 32-bit computer.
+<sup>&dagger;</sup> Starting with [!INCLUDE [sssql16-md](../../includes/sssql16-md.md)], [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] can no longer be installed on a 32-bit operating system. 32-bit computer values are listed for the assistance of customers running [!INCLUDE [ssSQL14](../../includes/sssql14-md.md)] and earlier. We recommend 1,024 as the maximum number of worker threads for an instance of [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] that is running on a 32-bit computer.
 
-<sup>2</sup> Starting with [!INCLUDE [ssSQL17](../../includes/sssql17-md.md)], the *Default Max Workers* value is divided by 2 for machines with less than 2 GB of memory.
+<sup>&dagger;&dagger;</sup> Starting with [!INCLUDE [ssSQL17](../../includes/sssql17-md.md)], the *Default Max Workers* value is divided by 2 for machines with less than 2 GB of memory.
 
 > [!TIP]  
 > For more information on using more than 64 logical CPUs, see [Best Practices for running SQL Server on computers that have more than 64 CPUs](../../relational-databases/thread-and-task-architecture-guide.md#best-practices-for-running-sql-server-on-computers-that-have-more-than-64-cpus).

docs/database-engine/configure-windows/configure-the-max-worker-threads-server-configuration-option.md

@@ -11,15 +11,15 @@ helpviewer_keywords:
   - "validating installations [SQL Server]"
 monikerRange: ">=sql-server-2016"
 ---
-# Validate a SQL Server Installation
+# Validate a SQL Server installation
 
 [!INCLUDE [SQL Server -Windows Only](../../includes/applies-to-version/sql-windows-only.md)]
 
 The [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] discovery report can be used to verify the version of [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] and the [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] features installed on the computer. The **Installed SQL Server features discovery report** displays a report of all products and features installed on the local server, for [!INCLUDE [ssVersion2000](../../includes/ssversion2000-md.md)] and later versions. The [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] features discovery report is available on the **Tools** page on the [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] Installation center.
 
 ## Run SQL Server features discovery report
 
-Launch the [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] Installation center, using the **Start** menu, point to **All Programs**, point to **Microsoft SQL Server \<Version Name>**, point to **Configuration Tools**, and select **SQL Server Installation Center**. To run the [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] features discovery report, select **Tools** in the left-hand navigation area of **SQL Server Installation Center**, and then select **Installed SQL Server features discovery report**.
+Launch the [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] Installation center, using the **Start** menu, point to **All Programs**, point to **Microsoft SQL Server \<Version Name>**, and select **SQL Server Installation Center**. To run the [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] features discovery report, select **Tools** in the left-hand navigation area of **SQL Server Installation Center**, and then select **Installed SQL Server features discovery report**.
 
 The [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] discovery report is saved to `%ProgramFiles%\Microsoft SQL Server\<nnn>\Setup Bootstrap\Log\<last Setup Session>`.
 

docs/database-engine/install-windows/validate-a-sql-server-installation.md

@@ -79,7 +79,7 @@ ms.topic: conceptual
 
  For the Oracle CDC, the LSN values stored in this table are based on the Oracle System Change Number (SCN) value associated with the change. The first 6 bytes of the LSN value is the original Oracle SCN number.  
 
- Also when using the Oracle CDC, the time columns (`tran_begin_time` and `tran_end_time`) store the UTC time of the change rather than the local time as it does with the regular SQL Server CDC. This ensures that daylight savings time changes do not impact the data stored in the lsn_time_mapping.  
+ Also when using the Oracle CDC, the time columns (`tran_begin_time` and `tran_end_time`) store the UTC time of the change rather than the local time as it does with the regular SQL Server CDC. This ensures that daylight saving time changes do not impact the data stored in the lsn_time_mapping.  
 
 ### cdc.xdbcdc_config
 

docs/integration-services/change-data-capture/the-oracle-cdc-databases.md

@@ -28,7 +28,7 @@ monikerRange: "=azure-sqldw-latest || >=sql-server-2016 || >=sql-server-linux-20
 | --- | --- | --- |
 | `name` | **sysname** | Name of the time zone in Windows standard format. For example, `Cen. Australia Standard Time` or `Central European Standard Time`. |
 | `current_utc_offset` | **nvarchar(12)** | Current offset to UTC. For example, `+01:00` or `-07:00`. |
-| `is_currently_dst` | **bit** | True if currently observing daylight savings time. |
+| `is_currently_dst` | **bit** | True if currently observing daylight saving time. |
 
 ## Remarks
 

docs/relational-databases/system-catalog-views/sys-time-zone-info-transact-sql.md

@@ -22,6 +22,10 @@ monikerRange: ">=sql-server-2016"
 
 This article summarizes the new features and enhancements for [!INCLUDE [sql-server-2025](../includes/sssql25-md.md)].
 
+ 
+
+> [!VIDEO https://www.youtube-nocookie.com/embed/3RgncKX6K9A]
+
 ## Get [!INCLUDE [sssql25-md](../includes/sssql25-md.md)]
 
 [Get SQL Server 2025 Preview](https://info.microsoft.com/ww-landing-sql-server-2025.html). Build number: 17.0.700.9.

docs/sql-server/what-s-new-in-sql-server-2025.md

@@ -160,9 +160,9 @@ First, verify the time zone name from the [sys.time_zone_info](../../relational-
 SELECT * FROM sys.time_zone_info WHERE name = 'Pacific Standard Time';
 ```
 
-The following example uses the [AT TIME ZONE](../queries/at-time-zone-transact-sql.md) syntax twice. The sample code creates a table `dbo.Audit`, adds data that spans multiple daylight savings time changes, and adds a new **datetimeoffset** column. We assume that the `AuditCreated` column is a ***datetime2** data type without offsets, and was written using the UTC time zone.
+The following example uses the [AT TIME ZONE](../queries/at-time-zone-transact-sql.md) syntax twice. The sample code creates a table `dbo.Audit`, adds data that spans multiple daylight saving time changes, and adds a new **datetimeoffset** column. We assume that the `AuditCreated` column is a ***datetime2** data type without offsets, and was written using the UTC time zone.
 
-In the `UPDATE` statement, the `AT TIME ZONE` syntax first adds UTC time zone offset to the existing `AuditCreated` column data, then converts the data from UTC to `Pacific Standard Time`, correctly adjusting the historical data for each past daylight savings time range in the United States.
+In the `UPDATE` statement, the `AT TIME ZONE` syntax first adds UTC time zone offset to the existing `AuditCreated` column data, then converts the data from UTC to `Pacific Standard Time`, correctly adjusting the historical data for each past daylight saving time range in the United States.
 
 ```sql
 CREATE TABLE dbo.Audit (AuditCreated DATETIME2(0) NOT NULL);