Consider the following guidelines when you add tables to a segmentation group:

If you do not include an application entity table in the segmentation group, the table remains visible and available without functional issues in the application. You will not achieve performance benefits for excluded tables.

Table indexes can help optimize smart partitioning performance and significantly reduce smart partitioning run time. Typically smart partitioning uses the index predefined by the application. If multiple potential indexes exist in the application schema for the selected table, you must register an index after you add the table to the segmentation group.

If the table does not have an index sufficient for partitioning, you can choose to create a temporary optimization index. When you configure a temporary optimization index, you give the index a name and specify the columns you want to use for indexing. The smart partitioning process creates the index dynamically when you run a segmentation policy and drops the index when segmentation is complete.

When you register a predefined index or create a temporary optimization index, you must decide when the partitioning process uses the index. You can configure the index to be used in the default segment creation process, non-default segment creation process, or both.