Staples Use Analytics and Mobile Apps to Provide Timely Visibility Into Key Business Metrics

SUMMARY:

Viewing an object's change journal information takes a long time to load, even when there are no entries in the change journal for that object.
 

STEPS TO REPRODUCE:

1. In Developer, log into a project.
2. Right-click an object and select Properties > Change Journal. Notice it takes a long time for the page to render. 

CAUSE:

Slowed performance may result from a large number of change journal entries already in the metadata.
Currently, there is no database index automatically created for database columns involved in the query of change journals. If you have not removed any of your old change journals, this means the change journal query is scanning all your database rows, which results in slowed performance.
 

ACTION:

To enhance performance, it's recommended to remove old change journal entries in the metadata.
If you do not want to remove old change journals, you can create your own database index. For example, if you have an Oracle metadata, you can use the following SQL statements to create indexes:

CREATE INDEX IX_JRNOBJS_OBJECT ON DSSMDJRNOBJS (OBJECT_ID);CREATE INDEX IX_JRNLNKS_OBJECT ON DSSMDJRNLNKS (OBJECT_ID);

These two statements creates indexes for the OBJECT_ID column in both the

DSSMDJRNOBJS 

and

DSSMDJRNLNKS 

tables. With an index, only relevant query are scanned when browsing an object's change journal. 
For metadata hosted on other databases, the statement syntax will likely be similar. For the exact syntax, referencing the database website. For more information on change journal entries, see the System Admin Guide.