(OO) Support Tip: Troubleshooting performance issues may involve OO's database

When troubleshooting performance issues in many OO environments, it has been found in a majority of cases that the bottleneck is the database.  A very common scenario is a slow load of the Run Explorer page.  If the customer reporting this issue is using Microsoft SQL Server, there is a high probabilty that fragmented database indexes are the root cause.  How to resolve?
Please contact Technical Support for the stored procedures and other utilities for the maintenance of HPE OO versions 10.22 to 10.80.  If the OO environment is version 10.10 or 10.60 to version 10.80 and the database is PostgreSQL 9.2 to 9.5, it is expected that these procedures and utilities will work.  These scripts have been tested and it was observed that defragmenting the index improved product performance.
Support matrix of databases and HPE OO versions:
Oracle 11g  - HPE OO 10.22 to 10.80
Oracle 12c - HPE OO 10.22 to 10.80
SQL Server 2008R2 - HPE OO 10.22 to 10.80
SQL Server 2012 - HPE OO 10.22 to 10.80
SQL Server 2014 - HPE OO 10.60 to 10.80
PostgreSQL 9.2 - 9.5 - HPE OO 10.10 and 10.60 to 10.80
Example environment running Microsoft SQL Server suggested steps to resolution:
- Microsoft SQL Server database which has a significat number of flow executions stored.
Run the scripts.  (1)  There is a query which will create a report with all indexes and their fragmentation status.  (2)  Run the defragmentation script.  (3)  Run the query from step one again and compare the results.
Please contact Technical Support if you have any questions.  
Please see the knowledge document at https://softwaresupport.hpe.com/km/KM03164894