Performance Tuning Guide > Tuning Customer Configurations for Performance > Best Practices for Business Objects Layer >
How the Check No Match Property Impacts Performance
In most cases, the Check No Match property of a Multi Value Link object definition (used to implement Primary ID fields) should be set to FALSE. Setting the Check No Match property to TRUE could negatively impact performance, especially in situations where most parent records do not have child records defined in an MVG.
The Check No Match property defines whether a separate query should be used to populate an MVG when no child record is found through a primary join.
- When Check No Match is set to FALSE, the application does the following:
- When Check No Match is set to TRUE, a separate SQL query is executed for each parent record in which the primary join did not find a primary child record. Doing this ensures that the multi-value field does not appear blank unless there are no child records. But executing these extra SQL queries decreases performance.
It is appropriate to set the Check No Match property to TRUE in the following cases:
- When the multi-value group allows records to be added without having to go through the MVG. For example, account addresses might actually be inserted through the Business Address multi-value group on the Contact business component instead of the Account business component.
- When records can be added to a detail business component through Siebel EIM.
For more information about configuring Multi Value Link object definitions, see Configuring Siebel Business Applications.