Database indexing

Indexing a database requires good understanding of the data, the user functions, and how the database is indexed. Indexes use key parts of data from a table in a binary structure to improve searching capability. Each record of data in the table must be associated with data in the index.

Indexing can greatly increase search speeds. However, a drawback of indexes is that each insert, update, or delete operation requires an update to the indexes. When tables include multiple indexes, each index can increase the time it takes to process table updates. If you want to reduce the number of indexes to improve processing speed, remove indexes that are least valuable for search purposes.

Some index types that are available on DB2®, Oracle Database, and Microsoft SQL Server are not available in the Database Configuration application. You can create and maintain these indexes from the command line to improve performance in specific cases. For example, on Oracle Database, you can create a bitmap index or a function-based index if you determine that these indexes can improve certain queries.

If you use these index types, the system administrator must remove any of these indexes before you configure the database changes. After the database is configured, the indexes must be replaced.

If you customize Maximo® Asset Management, you can change the way you select information from the database. For example, a customization might include additional tables and columns. If you customize Maximo Asset Management, compare indexes to the user functions that use them. Ensure that you implement the right balance of indexes.



Feedback