Responsibility for destination tables

Create the required tables before you configure and start a pipeline. Destination tables must use the column names and data types that the Data Catalog object schema defines. Apply the type mappings that the destination documentation provides.

You can use the Data Catalog API and the documented type mappings to create scripts or tools that generate DDL statements or create destination tables. Infor does not provide a table-generation utility. TheData Catalog API and the documented type mappings provide the information that is required to build such a utility.

You are responsible for ongoing management of the destination database and destination tables. Create and maintain indexes that support pipeline load operations. Tune the database configuration based on observed data-load patterns.

For pipelines that use the Upsert load method, a primary key or unique key index on the destination table is critical for performance. A missing index or a poorly defined index reduces write performance as table size increases.

For pipelines that use the Insert load method, review destination table indexes carefully. Each index adds write overhead to inserted rows. Monitor query performance and insert performance at the destination. Adjust the indexing strategy as data volume increases.