In some customer systems, performance may benefit from adding a custom index that the software does not add by default. Prior to adding a custom index, a customer should contact their first line of support in order to work with the Hyland Database Support Team for approval of the index.
An example of a custom index that may improve performance is the addition of an index on logdate for the hsi.transactionxlog table. This can help improve performance of some activities against the transactionxlog table, such as doing purges according to logdate. Additional information regarding this index can be found in the following post on the Community site: https://community.hyland.com/en/blog/posts/52711-improving-performance-when-purging-the-onbase-transaction-log-transactionxlog-table-in-sql-server.
Another example of a custom index that may improve performance is running OnBase Report Services. Depending on the report being executed, it is possible that the report would execute slowly and could benefit from a custom index being added. This may also depend on the configuration of the report. If adding a custom index may benefit the execution of the query, contact your first line of support for assistance in getting this index approved.
When engaging Hyland's Database Support Team for assistance in approving of a custom index, please provide the following:
-
The business case for the custom index.
-
The SQL statement(s) intended to benefit from the custom index.
-
The actual execution plan of the above statement, with and without the custom index in place.
Note:The custom index may be created in a non-production copy of the OnBase database for this purpose.
-
The CREATE INDEX statement to create the requested custom index.