Performance Issue: Long Loading Times

Overview

You may encounter performance issues with Everest, such as slow loading browsers, long execution times for queries, and delays in searching invoices.

This article provides the two methods to defragment and rebuild the indexes to improve the performance:

  1. SQL Server Management Studio
  2. Everest Interface
CAUTION! Please ensure that a complete backup of the database is complete before making any changes.

Information

  • Admin access is required to the Everest application and/or SQL Server Management Studio.
IMPORTANT!
  • Ensure all the users are logged out of Everest.
  • Ideally, defragmentation and reindex should be done after hours.
    (This is applicable for both methods.)

Process

Method 1: Via SQL Server Management Studio

  1. In SQL Server Management Studio, select the Everest database.
  2. Open New Query for the selected database.
  3. Execute the stored procedures on the EVEREST_xxxxxx database in the order given below:
    1. Exec DATABASE_REINDEX to reindex the database.
    2. Exec INDEX_DEFRAGMENTATION to defragment the index.
      Note: The stored procedures will display all changes made. Execution may take several hours, depending on the size of the database.

Back to top


Method 2: Via Everest Interface

  1. You can reindex the database and defragment the index directly from the Everest user interface.
  2. From the Everest user interface, go to Utilities Database Maintenance Rebuild Indexes. This executes the DATABASE_REINDEX procedure that triggers the reindexing process.
    Note: This should take from 30 min up to a couple of hours according to your database size, I/O rate.
  3. From the Everest user interface, go to Utilities Database Maintenance Defrag Indexes. This executes the INDEX_DEFRAGMENTATION procedure that triggers the index defragmentation process.
    Note: This needs to be executed on a more frequent basis than the index rebuild job.

Back to top


Note: If performance issues persist after following this procedure, please contact Support.

Comments

0 comments

Article is closed for comments.