You create the Sterling Selling and Fulfillment Foundation database, the Sterling Selling and Fulfillment Foundation tables, and their associated indexes. Additionally, the following DDL statements allow you to create a simple schema that is suitable for general use. You need to review and possibly modify these statements for production. Specifically:
Most customers use a subset of the broad functionality in Sterling Selling and Fulfillment Foundation. As a result, the base Sterling Selling and Fulfillment Foundation database schema with the default or starting set of indexes may have to be adjusted for your specific use. Therefore, you should validate the starting index set to see if they support your workloads.
As a suggestion, prior to production, you should conduct a system test where all the key screens, agents and APIs run against a copy of the production database. During this test, you can check if additional indexes are required and if there are any unused indexes you can disable or drop.
Please see the following sections on how to enable index monitoring:
Please follow the following convention when you create a new index:
First, make sure the index name does not end with the following suffix:
The convention above prevents situations where new base Sterling Selling and Fulfillment Foundation indexes have the same name as one of your custom index.
Secondly, to further differentiate custom indexes from the base, the custom index should start with EXTN_ as a prefix and Xnn in the index name. For example, if you add two indexes to the YFS_ORDER_HEADER table, the index names should be EXTN_ORDER_HEADER_X1 and EXTN_ORDER_HEADER_X2.