A couple of days ago I was doing some cleaning on some Azure SQL DBs and shrinking some files to lower the bill.
To check my progress I needed to check the size before/after the task in an easy way for multiple Azure SQL DBs.

Check Azure SQL DB storage space for 1 database

If you need to check the storage space being used by 1 Azure SQL DB, that is as easy as jumping on the portal, select the desired database and you can find the information in the Overview. This is shown below.

Portal View

Using T-SQL

If you prefer to use T-SQL and perhaps you already have SSMS/ADS open and ready to fire a query, despite being an Azure SQL DB, we can still use some old friends as sp_spaceused.


However, we can’t use sp_helpdb 'BlogDemo' (running on the context of the master database) as it seems it can see the named database we want.

The error message is:

Msg 15010, Level 16, State 1, Procedure sp_helpdb, Line 45 [Batch Start Line 0] The database ‘BlogDemo’ does not exist. Supply a valid database name. To see available databases, use sys.databases.

Interestingly enough, if we try to run the same command in the context of the user database BlogDemo we get a better error message:

Msg 40515, Level 15, State 1, Procedure sp_helpdb, Line 16 [Batch Start Line 0] Reference to database and/or server name in ‘master.dbo.sysdatabases’ is not supported in this version of SQL Server.

Getting an overview of all Azure SQL DBs

If you want to check the space being used by multiple databases that belong to the same server using the portal, that won’t be so funny.
You will need to jump from one database to the next one until you grab all the figures you want.

Using T-SQL

The previous T-SQL method shown just works per database too, meaning you also need to change your connection to grab the information from each database.

However, there is a different way to grab all the information by running a single query against the master database using the sys.resource_stats DMV .

The following code grabs the most recent information per database from the sys.resource_stats DMV.

	start_time AS 'LastCollectionTime', 
	storage_in_megabytes AS 'CurrentSize(MBs)',
	allocated_storage_in_megabytes AS 'AllocatedStorage(MBs)'
  FROM (
				ROW_NUMBER() OVER(PARTITION BY [database_name] ORDER BY start_time DESC) AS rn,
			FROM sys.resource_stats 
		) rs 
WHERE rn = 1


As we can see we get a row per database with the information on which time the collection happened, what was the current size and allocated storage in MB.


If, for example, you have been running some DBCC SHRINKFILE and you can’t see the new size right away, be aware that the data on the DMV is not real-time.
As stated in the documentation :

The data is collected and aggregated within five-minute intervals.

Hence, you may need to wait a couple of minutes before you see the new size, that you were expecting after your shrink process finished.

Thanks for reading!