20250303 ForcedPhysicalSectorSizeInBytes

Author: WilliamDAssafMSFT

docs/sql-server/install/hardware-and-software-requirements-for-installing-sql-server-2019.md

@@ -3,7 +3,7 @@ title: "SQL Server 2019: Hardware & software requirements"
 description: A list of hardware, software, and operating system requirements for installing and running SQL Server 2019.
 author: MikeRayMSFT
 ms.author: mikeray
-ms.date: 11/21/2024
+ms.date: 03/03/2025
 ms.service: sql
 ms.subservice: release-landing
 ms.topic: conceptual
@@ -192,7 +192,7 @@ Actual hard disk space requirements depend on your system configuration and the
 The supported storage types for data files are:
 
 - Local Disk
-    - [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] currently supports disk drives that have standard native sector sizes of 512 bytes and 4 KB. Hard disks with sector sizes larger than 4 KB might cause errors when attempting to store [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] data files on them. See [Hard disk drive sector-size support boundaries in [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)]](https://support.microsoft.com/kb/926930) for more information on hard disk sector-size support in [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)]. For more information, see [Troubleshoot errors related to system disk sector size greater than 4 KB](/troubleshoot/sql/admin/troubleshoot-os-4kb-disk-sector-size).
+    - [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] currently supports disk drives that have standard native sector sizes of 512 bytes and 4 KB. Hard disks with sector sizes larger than 4 KB might cause errors when attempting to store [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] data files on them. See [Hard disk drive sector-size support boundaries in [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)]](https://support.microsoft.com/kb/926930) for more information on hard disk sector-size support in [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)]. Currently, the `ForcedPhysicalSectorSizeInBytes` registry key is required to successfully install SQL Server on some newer storage devices with system disk sector size greater than 4 KB.
     - [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] failover cluster installation supports Local Disk only for installing the `tempdb` files. Ensure that the path specified for the tempdb data and log files is valid on all the cluster nodes. During failover, if the tempdb directories are not available on the failover target node, the [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] resource will fail to come online.
 - Shared Storage
 - [Storage Spaces Direct \(S2D\)](/windows-server/storage/storage-spaces/storage-spaces-direct-overview)

docs/sql-server/install/hardware-and-software-requirements-for-installing-sql-server-2022.md

@@ -173,7 +173,8 @@ The supported storage types for data files are:
 
        If you use advanced format disks that are physically formatted with 4,096 bytes, but expose a logical sector size of 512 bytes, you can read more about the behavior and recommendations in the Tech Community article [SQL Server - New drives use 4K sector size](https://techcommunity.microsoft.com/t5/sql-server-support-blog/sql-server-new-drives-use-4k-sector-size/ba-p/316277).
 
-       Hard disks with sector sizes larger than 4 KB can cause errors when attempting to store SQL Server data files on them. For more information, see [Troubleshoot errors related to system disk sector size greater than 4 KB](/troubleshoot/sql/database-engine/database-file-operations/troubleshoot-os-4kb-disk-sector-size).
+       Hard disks with sector sizes larger than 4 KB can cause errors when attempting to store SQL Server data files on them. See [Troubleshoot errors related to system disk sector size greater than 4 KB](https://support.microsoft.com/kb/926930) for more information on hard disk sector-size support in [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)]. Currently, the `ForcedPhysicalSectorSizeInBytes` registry key is required to successfully install SQL Server on some newer storage devices with system disk sector size greater than 4 KB.
+
   - [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] failover cluster installation supports Local Disk only for installing the `tempdb` files. Ensure that the path specified for the `tempdb` data and log files is valid on all the cluster nodes. During failover, if the `tempdb` directories aren't available on the failover target node, the [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] resource fails to come online.
 - Shared Storage
 - [Storage Spaces Direct \(S2D\)](/windows-server/storage/storage-spaces/storage-spaces-direct-overview)

docs/sql-server/install/hardware-and-software-requirements-for-installing-sql-server.md

@@ -340,7 +340,7 @@ Actual hard disk space requirements depend on your system configuration and the
 The supported storage types for data files are:
 
 - Local Disk
-    - [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] currently supports disk drives that have standard native sector sizes of 512 bytes and 4 KB. Hard disks with sector sizes larger than 4 KB might cause errors when attempting to store [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] data files on them. See [Hard disk drive sector-size support boundaries in SQL Server](https://support.microsoft.com/kb/926930) for more information on hard disk sector-size support in [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)]. For more information, see [Troubleshoot errors related to system disk sector size greater than 4 KB](/troubleshoot/sql/admin/troubleshoot-os-4kb-disk-sector-size).
+    - [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] currently supports disk drives that have standard native sector sizes of 512 bytes and 4 KB. Hard disks with sector sizes larger than 4 KB can cause errors when attempting to store [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] data files on them. See [Troubleshoot errors related to system disk sector size greater than 4 KB](https://support.microsoft.com/kb/926930) for more information on hard disk sector-size support in [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)]. Currently, the `ForcedPhysicalSectorSizeInBytes` registry key is required to successfully install SQL Server on some newer storage devices with system disk sector size greater than 4 KB.
     - [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] failover cluster installation supports Local Disk only for installing the `tempdb` files. Ensure that the path specified for the tempdb data and log files is valid on all the cluster nodes. During failover, if the tempdb directories are not available on the failover target node, the [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] resource fails to come online.
 - Shared Storage
 - [Storage Spaces Direct \(S2D\)](/windows-server/storage/storage-spaces/storage-spaces-direct-overview)

docs/t-sql/database-console-commands/dbcc-traceon-trace-flags-transact-sql.md

@@ -123,7 +123,7 @@ Trace flag behavior might not be supported in future releases of [!INCLUDE [ssNo
 | <a id="tf1260"></a>**1260** | Disable scheduler monitor dumps.<br /><br />**Scope:** Global only. |
 | <a id="tf1448"></a>**1448** | Enables the replication log reader to move forward even if the asynchronous secondaries haven't acknowledged the reception of a change. Even with this trace flag enabled the log reader always waits for the synchronous secondaries whose synchronization state is SYNCHRONIZED. The log reader doesn't go beyond the minimum acknowledged Log Sequence Number of the SYNCHRONIZED secondaries. This trace flag applies to the instance of [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)], not just an availability group, an availability database, or a log reader instance. This trace flag must be enabled on the publisher instance. It takes effect immediately without a restart. This trace flag can be activated ahead of time or when an asynchronous secondary replica fails.<br /><br />**Scope:** Global only. |
 | <a id="tf1462"></a>**1462** | Disables log stream compression for asynchronous availability groups. This feature is enabled by default on asynchronous availability groups in order to optimize network bandwidth. For more information, see [Tune compression for availability group](../../database-engine/availability-groups/windows/tune-compression-for-availability-group.md).<br /><br />**Scope:** Global only. |
-| <a id="tf1800"></a>**1800** | Enables [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] optimization when disks of different sector sizes are used for primary and secondary replica log files, in [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] Always On and Log Shipping environments. This trace flag is only required to be enabled on [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] instances with transaction log file residing on disk with sector size of 512 bytes. It's **not** required to be enabled on disk with 4-KB sector sizes. For more information, see [KB3009974](https://support.microsoft.com/kb/3009974).<br /><br />**Applies to:** [!INCLUDE [ssSQL11](../../includes/sssql11-md.md)] Service Pack 1 CU 13, [!INCLUDE [ssSQL11](../../includes/sssql11-md.md)] Service Pack 2 CU 3, [!INCLUDE [ssSQL14](../../includes/sssql14-md.md)] RTM CU 5, and later versions.<br /><br />**Scope:** Global only. |
+| <a id="tf1800"></a>**1800** | Enables [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] optimization when disks of different sector sizes are used for primary and secondary replica log files, in [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] Always On and Log Shipping environments. This trace flag is only required to be enabled on [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] instances with transaction log file residing on disk with sector size of 512 bytes. Trace Flag 1800 is not required to be enabled on disk with sector sizes larger than 4 KB. For more information, see [KB3009974](https://support.microsoft.com/kb/3009974), [KB2510009](https://support.microsoft.com/kb/2510009), and [KB926930](https://support.microsoft.com/kb/926930).<br /><br />**Applies to:** [!INCLUDE [ssSQL11](../../includes/sssql11-md.md)] Service Pack 1 CU 13, [!INCLUDE [ssSQL11](../../includes/sssql11-md.md)] Service Pack 2 CU 3, [!INCLUDE [ssSQL14](../../includes/sssql14-md.md)] RTM CU 5, and later versions.<br /><br />**Scope:** Global only. |
 | <a id="tf1802"></a>**1802** | Disables ACL change and impersonated access verification during database attach or detach operations. This can be useful when attaching a database and encountering access permission errors, such as error 5120.<br /><br />**Scope:** Global only. |
 | <a id="tf1819"></a>**1819** | Allows [backup to URL](../../relational-databases/backup-restore/sql-server-backup-to-url.md) to use a proxy server when accessing Azure block blobs. In addition to this trace flag, you must set the WinHTTP proxy configuration on the server with the [netsh.exe](/windows/win32/winsock/netsh-exe) utility on [!INCLUDE [winvista-md](../../includes/winvista-md.md)], [!INCLUDE [winserver2008-md](../../includes/winserver2008-md.md)], and later versions.<br /><br />**Scope:** Global or session or query (QUERYTRACEON). |
 | <a id="tf2301"></a>**2301** | Enable advanced decision support optimizations that are specific to decision support queries. This option applies to decision support processing of large data sets.<br /><br />**Scope:** Global or session or query (QUERYTRACEON). |