Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Performance improvements for child case queries

Updated on February 24, 2016

If your application makes heavy use of child case queries, performance might be improved by adding indexes to some of your database tables. To improve the performance of child case queries, add a database index to each of your work tables by using a multicolumn index on the pxCoverInsKey, pxObjClass, and pyStatusWork columns. For existing tables, it can be beneficial to add more columns to the index, depending on the nature of the queries in your application. Queries that do not use all the columns in the index should still take advantage of the database index, provided that the first filter criterion is pxCoverInsKey. Note that the more columns an index has, the slower the writes to the table are.

  • Previous topic NoSQL reporting performance considerations
  • Next topic Obtaining connection pool diagnostic data by using REST services

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us