You have an Azure SQL Database elastic pool that contains 10 databases.
You receive the following alert.
Msg 1132, Level 16, state 1, Line 1
The elastic pool has reached its storage limit. The storage used for the elastic pool cannot exceed (76800) MBs.
You need to resolve the alert. The solution must minimize administrative effort.
Which three actions can you perform? Each correct answer presents a complete solution.
NOTE: Each correct selection is worth one point.
To resolve the storage limit alert for your Azure SQL Database elastic pool while minimizing administrative effort, you can take the following actions: Increase the maximum storage of the elastic pool, which is straightforward and quick. Delete data from a database, which will free up space immediately, though it may need careful selection of data to be deleted. Remove a database from the pool, which also helps reduce the storage usage of the pool. By increasing the pool size or managing its content, you address the storage limit issue efficiently.
To resolve the storage limit alert for your Azure SQL Database elastic pool, you can: A. Increase the maximum storage limit of the elastic pool through Azure's management tools, which is a quick fix requiring minimal administrative effort. D. Enable data compression to reduce the storage size of tables and indexes, which can provide space savings without data loss. E. Shrink individual databases to release unused space back to the pool, although this should be done carefully to avoid performance issues due to fragmentation. Options B and C are less desirable as they involve deleting data or databases, which requires more effort and could impact your applications. Always consider the long-term implications and monitor storage after making changes to prevent future issues.
The answer D is wrong. For enable data compression, you need additional space. "The disk space requirements for enabling or disabling row or page compression are the same as for creating or rebuilding an index." https://learn.microsoft.com/en-us/sql/relational-databases/data-compression/data-compression?view=sql-server-ver16
I agree with chandlermonica833
A,C,E are the only options that will resolve the issue with elastic DB pools.
https://learn.microsoft.com/en-us/azure/azure-sql/database/elastic-pool-resource-management?view=azuresql Data compression is valid per the above article. Scroll a little ways down.
ACD, study the free material on the MS site.
C is not valid as in A, you already increased pool size.
Answer looks good - don't forget all these options could work but the question mentions the solutions must be the ones of "least administrative effort". For example option B Deleting data isn't as simple as it seems, you'd need to discover what data can be deleted, get permission from compliance teams on whether you can delete the "old/unused" data etc.
Isn't taking a DB out of the pool the same fix as deleting data?
https://stackoverflow.com/questions/52496146/azure-sql-server-error-the-elastic-pool-has-reached-its-storage-limit-the-sto https://learn.microsoft.com/en-us/azure/azure-sql/database/file-space-manage?view=azuresql-db increase resource size shrink database move a database to another tier
If we need to directly resolve the alert, I think the answer is correct.