Skip to content

Commit fb1c86b

Browse files
authored
Updates
1 parent ce637d9 commit fb1c86b

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

support/sql/database-engine/performance/performance-degradation-misaligned-io-sector-error.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -32,7 +32,7 @@ For databases with write-intensive workloads, aligning I/O operations can signif
3232

3333
You might experience performance degradation in SQL Server due to misaligned I/O operations if you encounter any of the following symptoms:
3434

35-
- **Slow synchronization or restore times**: Misaligned I/O operations can result in slower synchronization or restore times, especially in distributed SQL Server environments, such as Always On availability groups or log shipping.
35+
- **Slow synchronization or restore times**: Misaligned I/O operations can result in slow synchronization or restore times, especially in distributed SQL Server environments, such as Always On availability groups or log shipping.
3636
- **Error messages in the SQL Server error log**: Error messages related to I/O operations can indicate misalignment issues, such as:
3737

3838
`There have been # misaligned log IOs which required falling back to synchronous IO.`
@@ -51,7 +51,7 @@ fsutil fsinfo sectorinfo <volume path name>
5151

5252
The following screenshot shows the output of the `fsutil fsinfo sectorinfo` command for the `E:` drive, which has a sector size of 8 KB but a physical sector size of 4 KB, causing misaligned I/O operations:
5353

54-
:::image type="content" source="../../azure-sql/media/sql-installation-fails-error-azure-vm/8k-sector-size-example.png" alt-text="Screenshot of the command prompt output of the 8 KB sector size.":::
54+
:::image type="content" source="../../azure-sql/media/sql-installation-fails-error-azure-vm/8k-sector-size-example.png" alt-text="Screenshot of the command prompt output of the 8-KB sector size.":::
5555

5656
## Resolution
5757

0 commit comments

Comments
 (0)