The changes to the create table command are documented in “Creating a virtually-hashed table”. Changes to other commands include:
dbcc checktable – in addition to the regular checks it performs, checktable verifies that the preallocation performed during table creation is correct:
The number of pages preallocated matches the total number of data pages that must be allocated for the specified max hash key value.
The data pages are not preallocated in an extent where the preallocation scheme specifies that only OAM pages are allowed.
The OAM pages are allocated only in the first extent of an allocation unit (AU).
dbcc checkstorage – reports a soft fault if any data page that is not the first data page is empty for non-hashed tables. 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.
