Failure to rebuild search index

Rebuilding Search Index not only occurs when you restore the databases or manually perform it, but in fact also takes place every time you start the program. So any mishap hindering this process may lead to slowing down of the start up or even errors on searching the databases. For example, you cannot locate a client in the pool. One of the causes I encountered was that one of the databases was too big. That database was the Print Log (>100 MB after 1 year of usage). The solution is of course truncating the Print Log. The easiest way should have been "Export and delete log files" under Admin tab. But wait, export is ok but no single data is deleted, i.e. Bug! You then have to do this at the command prompt if you know how to input those DOS like commands. But if you are like me, a computer beginner, a GUI MySQL editor is mandatory. See next blog. Hence I strongly recommend you regularly back up and empty the log databases. You may ask the Patient database and the Consultation database will become really big one day, what will happen then? The answer I don't know. How about the vast amount of attachments uploaded? I was told the attachments are not involved in the rebuilding Search Index process and should not be worried.