PURCHASING > Utility > Database Maintenance > Re-index all tables
This utility (a “full” reindex) is used to rebuild indexes for all system tables, including the Main (Purchasing) Module and all optional modules. In addition, various other maintenance procedures are run during a full reindex.
If there is ever a need to reindex during regular business hours, use the Quick Reindex Utility, which skips the (optional) maintenance procedures and therefore takes less time to complete.
Alternatively, you can reindex tables in individual modules using the Reindex menu option under the Utility section of the applicable module.
Indexes are used to improve performance when searching for data in the system. Many database tables in SpendMap (and most database applications) have associated indexes.
Reindexing in the process of rebuilding indexes. When a table in a database is updated (e.g. when processing new transactions) the table itself is updated and the associated indexes are also updated. In a perfect world, reindexing would never be necessary but there are various reasons why indexes may become corrupt (i.e. not updated in accordance with the database table), such as hardware, software or network errors. If an index is corrupt, data may not be saved or displayed properly.
Therefore, it is good practice to reindex the system’s tables periodically.
|
If you are using the On-Demand (hosted, SaaS) version of SpendMap, the reindexing process will be scheduled and performed for you automatically. Please speak with SpendMap Client Services if you have any questions.
|
The recommended frequency for reindexing depends on the database option you are using. Under normal operating conditions, the recommended frequency is as follows:
However, you should also reindex if SpendMap ever displays a message indicating that an index is corrupt.
Also, if you are using the embedded (DBF) database option, the system should be re-indexed following any system error that has the potential to corrupt an index (even if no index-related message is encountered), such as when a user terminates the application abruptly (i.e. exits incorrectly), for example, due to a power failure, re-booting, a network server crash, etc.
|
There are two options to ensure that the system is reindexed periodically:
1.You can run the reindex procedure unattended. You can initiate the reindex procedure after hours so you don't inconvenience users.
2.You can enable a setting in user profile to remind one or more users (typically system administrators) to run the reindex procedure when logging into the system. |
