Skip to content

Commit 29e14d4

Browse files
Update support/sql/azure-sql/sql-deployment-fails-drive-not-ready.md
Co-authored-by: Masha Thomas (MSFT) <[email protected]>
1 parent 71b65e1 commit 29e14d4

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

support/sql/azure-sql/sql-deployment-fails-drive-not-ready.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -85,7 +85,7 @@ If you can't use another VM SKU without a RAW local SSD, consider the following
8585

8686
- Deploy the VM using a Windows Server-only image, [format and initialize the temporary NVMe drive](/azure/virtual-machines/enable-nvme-temp-faqs#how-can-i-format-and-initialize-temp-nvme-disks-in-windows-when-i-create-a-vm-), and then manually install SQL Server.
8787

88-
- If you choose to put `tempdb` on the local SSD, you must reinitialize the disk before starting SQL Server every time the VM is restarted or deallocated.
88+
- **If you choose to put `tempdb` on the local SSD, you must reinitialize the disk before starting SQL Server every time the VM is restarted or deallocated.**
8989

9090
- Deploy the SQL Server VM image, but configure `tempdb` to use a different drive than the ephemeral storage during the deployment. For example, you can configure `tempdb` to use the `C:` drive or remote storage drive.
9191

0 commit comments

Comments
 (0)