Fragmentation can also occur at the table or heap level. Data for indexes and tables is stored in separate pages within the database, and heap-level fragmentation can affect query performance just as index fragmentation can. Again, highly transactional tables that experience many inserts and deletes are prime targets for fragmentation. Tables such as hsi.lockkeys, hsi.loggeduser, hsi.registeredusers, hsi.doccheckout, and hsi.itemlc may have highly fragmented heaps. The sys.dm_db_index_physical_stats dynamic management view can be used to determine fragmentation.
If you determine a table is highly fragmented, it is recommended that you contact your first line of support to determine which option is appropriate for removing the heap fragmentation.