The value of row_count in sqlwatch_logger_disk_utilisation_table sums the number of rows across all indexes that belongs to the table.
Example:
I have a table with 100 rows and with 3 indexes. The row_count row_count in sqlwatch_logger_disk_utilisation_table is then 300.
Is this intended behavior or an omission?
I understand that the pages metrics there are summarized like this as well. It makes me sense, but for number of rows the same is slightly misleading…
What I did to fix this is that I updated the row 61 in [dbo].[usp_sqlwatch_logger_disk_utilisation_table] procedure as:
row_count = convert(real,sum(case when i.index_id IN (0,1) then p.rows else 0 end)),
Then it behaves more reasonably for me and collects number of rows just from clustered index or table (if it is heap)