Database parameters
Guidewire provides the following configuration parameters in the config.xml file that relate to the application database.
For information on editing config.xml and setting configuration parameters, see Working with configuration parameters.
DisableHashJoinPolicySearch
On an Oracle database, you can improve the performance of a policy search—if the search criteria include a first name, last name or a company name—by disabling a Hash Join.
Default: true
DisableIndexFastFullScanForPolicySearch
On Oracle, you can improve the performance of a policy search—if the search criteria include a first name, last name or a company name—by disabling an Index Fast Full Scan. This parameter has no effect on databases other than Oracle.
Default: true
DisableSequenceUtil
Disables the sequence utility class gw.api.system.database.SequenceUtil. Use this to ensure that any sequences in your code use some alternative mechanism for sequenced identifiers.
Default: false
DisableSortMergeJoinPolicySearch
On Oracle, you can improve the performance of a policy search—if the search criteria include a first name, last name or a company name—by disabling a Sort Merge Join. This parameter has no effect on databases other than Oracle.
Default: true
DiscardQueryPlansDuringStatsUpdateBatch
Whether to instruct the database to discard existing query plans during a database statistics batch process.
Default: false
IdentifyQueryBuilderViaComments
(SQL Server only.) Whether to provide comments with contextual information in certain SQL Select statements sent to the relational database. The comments are generated by instrumentation in higher level database objects created by using the query builder APIs.
The SQL comments are in the following format:
/* applicationName:ProfilerEntryPoint */The applicationName component of the comment is PolicyCenter.
The ProfilerEntryPoint component of the comment is the name of an entry point known to the Guidewire
profiler for that application. For example, ProfilerEntryPoint might have the value WebReq:ClaimSearch.
Default: true
See also
IdentifyORMLayerViaComments
(SQL Server only.) Whether to provide comments with contextual information in certain SQL Select statements sent to the relational database. The comments are generated by instrumentation in lower level objects, such as beans, typelists, and other database building blocks.
The SQL comments are in the following format:
/* applicationName:ProfilerEntryPoint */The applicationName component of the comment is PolicyCenter.
The ProfilerEntryPoint component of the comment is the name of an entry point known to the Guidewire
profiler for that application. For example, ProfilerEntryPoint might have the value WebReq:ClaimSearch.
Default: false
See also
UseOracleHintsOnMessageQueries
An Oracle database can experience improved performance if Oracle hints are used on queries for Message objects. This parameter affects Oracle databases only.
Default: true