The <databasestatistics> database configuration element

You use the <databasestatistics> element in database-config.xml to specify database statistic parameters that override the database defaults specified on the database. This element has the following attributes.

databasedegree

On Oracle, this attribute controls the degree of parallelism for each individual statement. The default is 1. PolicyCenter uses the value of this attribute for all statements.

SQL Server ignores the databasedegree attribute.

incrementalupdatethresholdpercent

Specifies the percentage of table data that must have changed since the last statistics process for the incremental statistics generation batch process to update statistics for the table.

The default is 10.

numappserverthreads

On both Oracle and SQL Server, the numappserverthreads attribute controls the number of threads that PolicyCenter uses to update database statistics for staging tables during import only. Command prompt tool table_import launches this import.

The value defaults to 1. If the value is greater than 1, then the PolicyCenter server assigns a table at a time to each thread as the thread becomes available. Each thread executes all of the database statistics statements for its assigned table.

For all other statistics generation operations, set the number of threads by specifying the number of workers for the database statistics work queue. Set the instances attribute on the <workers> subelement of the <work-queue> element for the database statistics work queue.

The default is 1.

samplingpercentage

On Oracle, this attribute controls the value of the estimate_percent parameter in the dbms_stats.gather_table_stats() SQL statements. You can set samplingpercentage to an integer from 1 to 100 to directly set the estimate_percent value. However, Guidewire recommends highly that you set the samplingpercentage value to 0 to set estimate_percent to AUTO_SAMPLE_SIZE. The default value is 0.

On SQL Server, the samplingpercentage attributes controls the value of the WITH FULLSCAN/SAMPLE PERCENT clause in the UPDATE STATISTICS statements. A value of 100, the default, translates into WITH FULLSCAN, as does a value of 0.

The default is 0.
useoraclestatspreferences

On Oracle, this attribute sets the database statistics preferences to be able to use the Oracle Autotask infrastructure instead of the DBStats batch process from PolicyCenter. The default is false, which requires that you disable the Autotask and schedule DBStats batch processing in its place. Changes to the value of this attribute only take effect during an application upgrade.

The values you set for these attributes apply to all the tables in the database. You can fine tune these values and set specific values on individual tables by using the <tablestatistics> subelement. Setting values on a specific table overrides the values set on the database for just that table.