Kenneth Fisher shows off my favorite built-in SSMS report:
Every now and again you need to know how big a table is. Or several tables. Or all of the tables. Number of rows is frequently handy when you’re going to create a new index or otherwise modify the table. The amount of space used by the indexes can be helpful in deciding how much space you need to do a re-index. The tables with the most unused space is nice to know if you have a problem with ever growing heaps.
In the past my go to solution here was sp_spaceused. It’s a really handy procedure.
USE AdventureWorks2014; GO EXEC sp_spaceused 'Person.Person'; GOGreat information but it has a few problems. You can only run it for one table at a time (sp_msforeachtable is a workaround, if undocumented), the file sizes aren’t consistent (sometimes KB, sometimes MB or even GB), and it only returns the name of the object but not the schema. So if there is the same table name under multiple schemas it can get tricky.
Read on for how to access and use this report.
[…] are cases when you wouldn’t want to use the Disk Usage By Table report, so here is a viable […]