SQL Server Partition Details Custom Reports provides SQL Server Management Studio users with custom reports that lists table and indexed view row counts, partition boundaries and other details. This RDL uses the standard Custom report framework introduced in SQL Server 2005 SP2.
- Basic report lists tables and indexed views in the context database including:
- Object name
- Index name
- Rows (object and partition level)
- Partition Number
- Partition Lower Boundary (partitioned objects only)
- Partition Upper Boundary (partitioned objects only)
- Partition Function Range (LEFT or RIGHT) (partitioned objects only)
- Partition Scheme (partitioned objects only)
- File Group Name
- Enhanced report includes all information in basic report plus:
- Used Pages
- Used Space (KB)
- Reserved Pages
- Reserved Space (KB)
SQL Server Management Studio 2005 SP2 or above.
Copy files "Partition Details.rdl" and "Partition Details With Space Information.rdl" to a folder that is accessable to the SQL Server Management Studio client. This may be a local folder or network share.
Important Security Note
Before running this or any other SSMS custom report obtained from a third party, view the RDL file source using a text editor or SQL Server Business Intelligence Development Studio to ensure the SQL does not contain malicious code.
The query used in this report selects from system catalog views so the current user requires VIEW DEFINITION permission on the reported objects. This is the same permission needed for objects to be visible in the SSMS Object Explorer tree so no additional user security needs to be granted.
To run the report for a single table or indexed view, right-click on the desired object in SSMS Object explorer. Select "Custom Reports..." and browse to the location of the "Partition Details.rdl" file. The report file location will be remembered and included in the recently used list of that node type going forward for convenience.
The report will include all tables and indexed views in the current database when run in the context of any other node type (not a table or view) under the Databases folder. If the report is run outside of a database folder tree context, an error will be displayed indicating that the DatabaseName vaue is missing.