TPC Benchmark
TM
H Standard Specification Revision 3.0.0 Page 20
than days, a partition boundary may extend beyond the minimum or maximum boundaries as established in
that table’s data characteristics as defined in Clause 4.2.3.
• The directives must allow the insertion of values of the partitioning column(s) outside the range covered by
the minimum and maximum values, as required by Clause 1.5.13.
Multiple-level partitioning of base tables or auxiliary structures is allowed only if each level of partitioning satisfies
the conditions stated above and each level references only one partitioning field as defined above. If implemented,
the details of such partitioning must be disclosed.
1.5.5 Physical placement of data on durable media is not auditable. SQL DDL that explicitly partitions data vertically is
prohibited. The row must be logically presented as an atomic set of columns.
Comment: This implies that vertical partitioning which does not rely upon explicit partitioning directives is
allowed. Explicit partitioning directives are those that assign groups of columns of one row to files, disks or areas
different from those storing the other columns in that row.
1.5.6 Except as provided in Clause 1.5.7, logical replication of database objects (i.e., tables, rows, or columns) is not
allowed. The physical implementation of auxiliary data structures to the tables may involve data replication of
selected data from the tables provided that:
• All replicated data are managed by the DBMS, the operating system, or the hardware;
• All replications are transparent to all data manipulation operations;
• Data modifications are reflected in all logical copies of the replicated data by the time the updating
transaction is committed;
• All copies of replicated data maintain full ACID properties (see Clause 3: ) at all times.
1.5.7 Auxiliary data structures that constitute logical replications of data from one or more columns of a base table (e.g.,
indexes, materialized views, summary tables, structures used to enforce relational integrity constraints) must
conform to the provisions of Clause 1.5.6. The directives defining and creating these structures are subject to the
following limitations:
• Each directive may reference no more than one base table, and may not reference other auxiliary structures.
• Each directive may reference one and only one of the following:
o A column or set of columns listed in Clause 1.4.2.2, whether or not it is defined as a primary key
constraint;
o A column or set of columns listed in Clause 1.4.2.3, whether or not it is defined as a foreign key constraint;
o A column having a date datatype as defined in Clause 1.3.
• Each directive may contain functions or expressions on explicitly permitted columns
No directives (e.g. DDL, session options, global configuration parameters) are permitted in TPC-H scripts whose
effect is to cause the materialization of columns (or functions on columns) in auxiliary data structures other than
those columns explicitly permitted by the above limitations. Further, no directives are permitted whose effect is to
cause the materialization of columns in auxiliary data structures derived from more than one table.
Comment: Database implementations of auxiliary structures generated as a result of compliant directives usually
contain embedded pointers or references to corresponding base table rows. Database implementations that
transparently employ either ‘row IDs’ or embedded base table ‘Primary Key’ values for this purpose are equally
acceptable.
In particular, the generation of transparently embedded ‘Primary Key’ values required by auxiliary structures is a
permitted materialization of the ‘Primary Key’ column(s). ‘Primary Key’ and ‘Foreign Key’ columns are listed in
Clause 1.4.1.