Hi Handian Sudianto,
Thanks for reaching out to Microsoft Q&A.
Please consider the following for narrowing down the issue.
- The metrics that report storage usage within Azure SQL may not update immediately. Although you've truncated tables and physically reduced the amount of storage being used, the system metrics that azure SQL uses to determine if a decrease in storage capacity is permissible might not yet reflect these changes.
- SQL Server often reserves space for future growth and operations, which might not be immediately freed up in the storage metrics after data deletion or truncation. This reserved space can affect your ability to reduce the size of the storage pool.
- If the elastic pool manages multiple databases, decreasing the storage might require data to be redistributed within the pool. The system might prevent storage reduction if it anticipates potential data distribution constraints or if not all databases within the pool have reduced their footprint equally.
- Remember that Azure also considers snapshot and backup storage in its capacity calculations. If there are snapshots or backups that haven't been cleaned up or reduced, this could be affecting the overall storage calculation.
Possible steps to resolve:
- Give the system some time to update its metrics. Monitor the storage usage metrics via the Azure portal to see if they adjust over the next few hours.
- Check any backups or snapshots that may be contributing to the storage usage.
Please 'Upvote'(Thumbs-up) and 'Accept' as an answer if the reply was helpful. This will benefit other community members who face the same issue.