Bookshelf Home | Contents | Index | PDF |
Siebel Performance Tuning Guide > Tuning Customer Configurations > Performance Guidelines for Business Objects Layer > How the Check No Match Property Impacts PerformanceThis topic is part of Performance Guidelines for Business Objects Layer. In most cases, the Check No Match property of a Multi Value Link object definition (used to implement Primary ID fields) must 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 must be used to populate an MVG when no child record is found through a primary join.
It is appropriate to set the Check No Match property to TRUE in the following cases:
For more information about configuring Multi Value Link object definitions, see Configuring Siebel Business Applications. |
Siebel Performance Tuning Guide | Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices. | |