Operational stats mention the same table twice, what does this mean?

Question

While investigating why my application mentions deadlocking, I fell upon this question, whose answer mentions an SQL query, showing operational logs. However, the results of that query contain the same tablename twice, for some tables.

How should I interpret that result?

Hereby the mentioned SQL query:

SELECT t.name AS [TableName],
   fi.page_count AS [Pages],
   fi.record_count AS [Rows],
   CAST(fi.avg_record_size_in_bytes AS int) AS [AverageRecordBytes],
   CAST(fi.avg_fragmentation_in_percent AS int) AS [AverageFragmentationPercent],
   SUM(iop.leaf_insert_count) AS [Inserts],
   SUM(iop.leaf_delete_count) AS [Deletes],
   SUM(iop.leaf_update_count) AS [Updates],
   SUM(iop.row_lock_count) AS [RowLocks],
   SUM(iop.page_lock_count) AS [PageLocks]
FROM sys.dm_db_index_operational_stats(DB_ID(),NULL,NULL,NULL) AS iop
JOIN sys.indexes AS i ON iop.index_id = i.index_id AND
                       iop.object_id = i.object_id
JOIN sys.tables AS t ON i.object_id = t.object_id AND
                      i.type_desc IN ('CLUSTERED', 'HEAP')
JOIN sys.dm_db_index_physical_stats(DB_ID(), NULL, NULL, NULL, 'SAMPLED') AS fi ON fi.object_id=CAST(t.object_id AS int) AND
                                                                                 fi.index_id=CAST(i.index_id AS int)
GROUP BY t.name, fi.page_count, fi.record_count, fi.avg_record_size_in_bytes, fi.avg_fragmentation_in_percent
ORDER BY [RowLocks] desc

Answer 1

Of course it may return the same TableName twice (or more), because the query you're using is looking at system views that return information about indexes, and one table can have multiple indexes on it.

sys.dm_db_index_operational_stats():

Returns current lower-level I/O, locking, latching, and access method activity for each partition of a table or index in the database.

sys.dm_db_index_physical_stats(DB_ID():

Returns size and fragmentation information for the data and indexes of the specified table or view in SQL Server. For an index, one row is returned for each level of the B-tree in each partition. For a heap, one row is returned for the IN_ROW_DATA allocation unit of each partition. For large object (LOB) data, one row is returned for the LOB_DATA allocation unit of each partition. If row-overflow data exists in the table, one row is returned for the ROW_OVERFLOW_DATA allocation unit in each partition.