Skip to content

Update storage-configuration.md #10191

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from
Closed

Update storage-configuration.md #10191

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Update storage-configuration.md 
Add limitations about extending disks for storage pools
  • Loading branch information
@DBAlberto
DBAlberto authored Oct 5, 2025
commit ab991a6b4bcaac8815e2163a2e5ad07c089f2283
2 changes: 2 additions & 0 deletions azure-sql/virtual-machines/windows/storage-configuration.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -116,6 +116,8 @@ Selecting **Configure** opens the **Extend Data drive** page, allowing you to ch

If you've already reached the maximum disks supported for a particular VM size, you might need to [Resize the VM](/azure/virtual-machines/sizes/resize-vm).

When extending a storage pool for a SQL Server virtual machine via the Azure portal, the SQL IaaS Agent extension enforces a minimum disk addition requirement based on the number of columns configured in the original storage pool. This column count corresponds to the number of data disks provisioned during initial deployment. For example, if the storage pool was created with four premium SSD disks, any subsequent expansion must include at least four additional disks to maintain the integrity and performance characteristics of the striped storage configuration.

<a id="modifying-tempdb"></a>

### Modify tempdb
Expand Down