MySQL (but applies to other SQL databases)
This knowledgebase (KB) article is provided for informational purposes only and as a courtesy service to you, our customer. GWAVA Technical Support does not have any database administration (DBA) expertise, nor does it provide DBA services or support. GWAVA is not responsible for the results of implementing any of the concepts contained in this KB article. Implementation of any of the concepts suggested in this KB article shall be done entirely at your own and sole risk, and GWAVA does not provide any kind of warranties whatsoever resulting from your decision of implementing any of the KB articleâs concepts. It is up to you to do any research and to ensure yourself that any implementation and setup of any of the KB articleâs concepts in your database system is correctly and properly executed. It is imperative that you have backups of your database system and storage directory before making any implementation. If you donât have any DBA expertise, you should consult with a DBA expert before any implementation of the KB articleâs concepts. Under no circumstances, shall GWAVA, or any of its employees, be liable, in contract, tort, delict or otherwise, whether negligence is provable or not, for any direct, indirect, incidental, special, punitive, consequential or other damages, loss, cost or liability whatsoever that would result from or are related to the implementation of any of the concepts suggested in the KB article.
To the extent permitted by applicable law, GWAVA shall not be liable to you for any special, consequential, direct, indirect or similar damages, including any loss of data, arising out from migrating any type of messages, attachments, database, metadata in your Retain system to another server and/or location.
This article is mainly for GWAVA support egineer purposes. When indexing messages their attachments, Retain keeps track of each messages' index "state". Was it ever indexed? Was it indexed by the old Retain 3 indexer? Was it indexed by the new Retain 4 indexer (for Retain 4 customers)? Were there any errors or problems getting some of the message content (i.e., certain attachments) indexed?
Retain stores a code in the t_message table in the f_indexed field to track that information.
To see a count on the number of messages for each index value in the database, run this query (see "How to Login to Your Retain MySQL Database and Run Queries"):
select f_indexed, count(*) from t_message group by f_indexed;