Azure Elastic Pool has a huge allocated space compared to used space
Not really C# related, but maybe someone can help me.
I have multiple databases in an Azure SQL Elastic Pool. The total used space is around 100GB, but the allocated space across the databases is about 300GB. I'm wondering what the best way to handle this excess allocated space is. Should I use DBCC SHRINKDATABASE, DBCC SHRINKFILE, or another method? Also, how frequently (if at all) should these commands be run in an elastic pool scenario?
1 Reply
What's the actual issue here?