Skip to content

Commit 0e90904

Browse files
authored
Updates from editor
1 parent 8a79858 commit 0e90904

1 file changed

Lines changed: 5 additions & 5 deletions

File tree

support/sql/database-engine/database-file-operations/troubleshoot-os-4kb-disk-sector-size.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -86,7 +86,7 @@ Cannot use file 'data file path', because it is on a volume with sector size 819
8686

8787
During service startup, SQL Server begins the database recovery process to ensure database consistency. Part of this database recovery process involves consistency checks on the underlying filesystem before you try to open system and user database files.
8888

89-
Some new storage devices and device drivers exposes a disk sector size greater than the supported 4-KB sector size.
89+
Some new storage devices and device drivers expose a disk sector size greater than the supported 4-KB sector size.
9090

9191
When this occurs, SQL Server will be unable to start due to the unsupported file system as SQL Server currently supports sector storage sizes of 512 bytes and 4 KB.
9292

@@ -121,7 +121,7 @@ Additionally, be aware of the Windows support policy for file system and storage
121121
1. Run Registry Editor as an administrator.
122122
1. Navigate to `Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\stornvme\Parameters\Device`.
123123
1. Select **Edit** > **New** > **Multi-String value** and name it as `ForcedPhysicalSectorSizeInBytes`.
124-
1. Right click the name, select **Modify**, and type `* 4095` in the **Value data** field.
124+
1. Right-click the name, select **Modify**, and type `* 4095` in the **Value data** field.
125125
1. Select **OK** and close Registry Editor.
126126

127127
### [Command Prompt](#tab/command-prompt)
@@ -133,7 +133,7 @@ Additionally, be aware of the Windows support policy for file system and storage
133133
REG ADD "HKLM\SYSTEM\CurrentControlSet\Services\stornvme\Parameters\Device" /v "ForcedPhysicalSectorSizeInBytes" /t REG_MULTI_SZ /d "* 4095" /f
134134
```
135135

136-
1. Run the following command to validate if the key was added successfully:
136+
1. Run the following command to validate if the key is added successfully:
137137

138138
```console
139139
REG QUERY "HKLM\SYSTEM\CurrentControlSet\Services\stornvme\Parameters\Device" /v
@@ -149,14 +149,14 @@ Additionally, be aware of the Windows support policy for file system and storage
149149
New-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Services\stornvme\Parameters\Device" -Name "ForcedPhysicalSectorSizeInBytes" -PropertyType MultiString -Force -Value "* 4095"
150150
```
151151

152-
1. Run the following command to validate if the key was added successfully:
152+
1. Run the following command to validate if the key is added successfully:
153153

154154
```Powershell
155155
Get-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Services\stornvme\Parameters\Device" -Name "ForcedPhysicalSectorSizeInBytes"
156156
```
157157
---
158158

159-
- If you don't add the registry key and you have multiple drives on this system, you can specify a different location for the database files after the installation of SQL Server is complete. Make sure that drive reflects a supported sector size when querying the `fsutil` commands. SQL Server currently supports sector storage sizes of 512 bytes and 4,096 bytes.
159+
- If you don't add the registry key and you have multiple drives on this system, you can specify a different location for the database files after the installation of SQL Server is complete. Make sure that the drive reflects a supported sector size when querying the `fsutil` commands. SQL Server currently supports sector storage sizes of 512 bytes and 4,096 bytes.
160160

161161
## More information
162162

0 commit comments

Comments
 (0)