Consistency checks and performance

For very large databases, running consistency checks can have a major negative effect on PolicyCenter performance. For example, some consistency check queries use a large amount of temporary space. Be aware that running consistency tests during server start up:

  • Can take a large amount of time to complete
  • Can impact performance severely
  • Can possibly time out on large data sets

Guidewire recommendations

In working with consistency checks, Guidewire recommends the following:
  • For development environments with very small data sets, it is possible to enable consistency checks to run each time the PolicyCenter server starts.
  • For development or production environments with large data sets, run the consistency checks against a copy of the database.

Deprecated checker attribute

Guidewire deprecates the use of the checker attribute on <database-config> and recommends that you do not use this attribute in most situations. Set the checker attribute to false under most circumstances. Only set the checker to true in development environments with very small test data sets.