Setup for Tables

A case table and any tables joined to it that are not set up properly can have a significant impact on the performance of the wizard, that is, they may significantly slow down gathering table statistics and other mining tasks. Setup requirements depend on how the table or view is used:

Case Table

Any Single Key attribute selected as a Unique Identifier should have an index; if there is no index, the wizard may be non-performant.

If a case table is a view, the query that defines it should rely on constraints and indexes of the underlying tables.

Joined Tables

Any tables or views that are joined to the case table should be set up with appropriate indexes on join keys. Usually, defining tables with constraints (foreign keys and/or primary keys) implies automatic indexing, but this can be overridden at table creation time.