How to rebuild indexes


Indexes are files that contain information used to quickly retrieve records in a database table. They are crucially important to the performance of database operations. Without indexes, everything would slow to a crawl, but with them performance is snappy.


While indexes rarely need attention, it is possible for an index problem to occur. An unprotected power outage at just the moment an index is being changed can damage files and indexes as well. It's also possible, but unlikely, that another program on your computer can damage H2OS's files, including index files.  


While hoping you'll never need to use this procedure, it is possible to repair your index files using H2OS.


The Librarian -> database maintenance -> rebuild indexes menu has 3 options for rebuilding indexes used with your H2OS database tables.  In all cases the operation consists of deleting existing indexes and rebuilding them from scratch (versus attempting to repair them).


- customer database

- job tickets database

- all other databases






If you select CURRENT DATABASE, it will delete and re-build indexes for your customers (aka CUSTLIST, with the file name of realcus.dbf. Similarly. the JOB TICKETS DATABASE option will delete and re-create indexes for the job tickets database (aka TRACKLOG, with the file name of REALCUST.TL).


If you select ALL DATABASES, the utility will search these folders for all DBFs that have indexes, and for each database it finds that has an index (CDX file), it will delete and re-create the indexes.




When the re-building process completes, a message will show the number of databases CDX's  re-created for, plus the count of any it skipped (no CDX) or missed (busy, read-only, etc.).



This process generates a report of it's results (the ALL OTHER DATABASES REPORT option on the index menu, see above).


When this process completes, it does a shutdown (necessary because all databases are closed).