Recommendations for running database consistency checks

Guidewire recommends that you run the database consistency checks on a regular basis to identify potential problems. For example, run database consistency checks:

• Before importing data into a production database
• Before and after a database upgrade
• Weekly after a new PolicyCenter deployment
• Monthly after stabilization of a new PolicyCenter deployment
• Monthly while testing imported data that you converted from a legacy system
• Monthly after you have moved the converted data to a production database

Best practice

It is possible to trigger the execution of database consistency checks as the application server starts, by setting a database attribute in file database-config.xml. However, Guidewire does not recommend that you use this method of automatically running consistency checks as a general rule, especially in a production environment. The execution of consistency checks is very resource intensive and impacts server performance significantly. Only trigger the execution of consistency checks at server start in a development environment that contains a very small data set.

Instead, Guidewire recommends that you execute consistency checks from the Server Tools Consistency Checks screen in PolicyCenter.