The dbcc checktable and dbcc checkstorage commands support virtually hashed tables.
Data pages are not allocated in an extent reserved for OAM pages as per the layout.
The OAM pages are allocated only in the first extent of an allocation unit.
dbcc checkstorage – reports a soft fault if any data page that is not the first data page is empty for tables that are not hashed. However, dbcc checkstorage does not report this soft fault for the hashed region of a virtually hashed table. Any data page in the hashed region of a virtually hashed table can be empty.