There must be at least one clustered index for record data.

Therefore, only one clustered index can be created on a given database table.

Drop any of the new clustered indexes that you do not need, per your database design.

Each relation can have a single clustered index and many unclustered indices.

A table without a clustered index is stored in an unordered heap structure.

In this case there is no clustered index, so the "Statistics for table:" is used.

Records in the clustered index contain fields for all user-defined columns.

If the user has not defined a primary key for a table, then each clustered index record contains also a 6-byte row id field.

Drop clustered indexes on any tables on that 500M fragment.

If a table is large, the clustered index architecture often saves a disk i/o when compared to the traditional solution.

Create clustered indexes on all the tables which are currently on the 500M fragment.

Each secondary index record contains also all the fields defined for the clustered index key.

InnoDB uses this primary key value to search for the row from the clustered index.

In clustered indices with duplicate keys, the dense index points to the first record with that key.

They are stored in separate B+tree from the clustered index keyed by long value id and byte offset.

Of course, if a table does not have a clustered index, nonclustered indexes continue to use the physical record identifiers to point to the data pages.

When multiple databases and multiple tables are joined, it's referred to as a cluster (not to be confused with clustered index described above).

Statistics for clustered indexes on APL tables appear under table statistics.

In ESE, the clustered index must be unique and is referred to as the primary index.

Firebird makes all indices of the database behave like well-tuned "clustered indexes" used by other architectures.

Accessing a row through the clustered index is fast, because the row data will be on the same page where the index search leads us.

Every InnoDB table has a special index called the clustered index where the data of the rows is stored.

On some RDBMS a primary key generates a clustered index by default.

Clustered indexes in ESE must also be primary, meaning that the index key must be unique.

GUIDs are commonly used as the primary key of database tables, and with that, often the table has a clustered index on that attribute.