VertiPaq Analyzer is useful to analyze VertiPaq storage structures for a data model in Analysis Services Tabular.
A complete description and short tutorial is available in the article Data Model Size with VertiPaq Analyzer.
You can analyze a Power Pivot data model by restoring it in Analysis Services.
The current version is not compatible with the Power BI Designer data model.
Version 1.9 fixed issues managing relationships created with Tabular Editor (1200 only) and improved syntax error handling calling DAX Formatter.
Version 1.8 fixed minor issues in calculation, in particular for evaluation relationships’ size.
The ZIP file includes Version 1.8 for Excel 2016 and version 1.6 for Excel 2013. The 1.8 version works for compatibility levels 1200 or higher.
Version 1.7 introduce two models, one for compatibility level 1103 (SSAS 2012/2014) and one for compatibility level 1200 (Power BI/SSAS 2016). The latter shows more information about relationships and a complete list of measures, calculated columns, and calculated tables, including their DAX expressions that can be formatted with a single click (code borrowed from Power Pivot Utilities for this feature – thanks Bertrand! Read more in the updated article Data Model Size with VertiPaq Analyzer.
UPDATE 2016-09-22: Microsoft fixed the bug of DMV in SQL Server 2016 RTM CU2. Now VertiPaq Analyzer 1.6 works correctly also with SSAS Tabular models in compatibility level 1200.
Version 1.6 fixed an issue displaying column’s cardinality in Columns worksheet. Microsoft fixed the issue of compatibility models 1200 in Power BI Version 2.38.4491.282 (August 2016). Still waiting for a fix for Analysis Services 2016 RTM.
UPDATE 2016-06-26: VertiPaq Analyzer does not report correctly the column size for database in compatibility model 1200 deployed in Analysis Services 2016 RTM (build 13.0.1601.5) – this is caused by a bug in Analysis Services, we are waiting for a fix from Microsoft.
Version 1.5 fixed a small issue displaying the combination of table-column name in a single column, which was displaying column id instead of column name in ColumnKey attribute. Now we use TableColumn attribute in Columns worksheet.
Version 1.4 now includes encoding type and it fixes column names if they have been renamed in the data model.
Version 1.3 now handles correctly renamed tables and renamed columns in the data model.