Does the database require indexes on primary and/or foreign keys? TPC-D as a benchmark does not require indexes (Clause 1.4), but it permits them (Clause 1.5).
3.7: Are the queries designed to work without indexes? Only a small number of the queries, notably query 1, were designed to be run without indexes. Usually, some indexing will be needed to reduce the elapsed time of queries. 3.8: Are there any rules governing the creation of secondary access structures such as B-tree indexes? TPC-D does not dictate a particular set of indexes nor does it place limits on the number and type of indexes used in a TPC-D implementation. The only requirement is that indexes (and other auxiliary data access structures) reflect update activity, be managed transparently and maintain ACID properties (see Clause 1.5). 3.9: Are implementations with different indexing strategies comparable? Yes. TPC-D was designed to assign some cost or penalty for the creation and maintenance of auxiliary data structures so that test sponsors are not lured into creating huge numbers of indexes. There are four ways in which an implementor “pays” for indexing: 1.
Related Questions
- Does the database require indexes on primary and/or foreign keys? TPC-D as a benchmark does not require indexes (Clause 1.4), but it permits them (Clause 1.5).
- Is database objects (tables, fields, indexes and foreign keys) remapping for synchronization possible?
- Does TPC-D require referential integrity on primary keys?
