Answers.Body: <p>Lobo, took your suggestion and converted to InnoDB. We were getting hit with about on failure a month. It has been about 3 weeks, we have not seen a problem. We moved the server to a solid state drive a number of months ago to improve reliability and response time. I don't have any statistics on performance but in general the online system does not write huge amounts of data to the log except when doing a batch operation like a mass mailing,  </p>
  
  <p>I would suggest making all new CiviCrm installations use InnoDB to improve reliability which is often much more important then time to log updates.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-05-30T11:40:49.623Z
Answers.LastActivityDate: 2015-05-30T11:40:49.623Z
Answers.UserDisplayName: user469
Answers.Body: <p>A few orgs who use logging on fairly high volume sites have modified the logging tables to either use MyISAM or InnoDB and have had fairly good success with it. Can you please report back if you adopt this approach and your success with it</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-05-08T00:13:40.087Z
Answers.LastActivityDate: 2015-05-08T00:13:40.087Z
Answers.UserDisplayName: Donald Lobo
Body: <p>Running a Drupal site with CiviCRM Logging enabled.  It seems like once a month we get a crash. On investigation one of the log tables is corrupted. Since the tables are type Archive MYSQL provides very limited tools. </p>
  
  <p>The normal fix is to remove the data from the sick table or completely deleting the sick table and rebuilding. Any suggestions for preventing the issue or recovering from the problem</p>
  
Tags: <mysql><logs><db-logging><mysql-archive-format>
Title: What causes periodic database errors while using logging, and what should I do about it?
ThreadText: # What causes periodic database errors while using logging, and what should I do about it?
  
  (Asked by: username_0 on 2015-05-07)
  
  Running a Drupal site with CiviCRM Logging enabled. It seems like once a month we get a crash. On investigation one of the log tables is corrupted. Since the tables are type Archive MYSQL provides very limited tools.
  
  The normal fix is to remove the data from the sick table or completely deleting the sick table and rebuilding. Any suggestions for preventing the issue or recovering from the problem
  
  **Tags:** mysql, logs, db-logging, mysql-archive-format
  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_1 on 2015-05-08. Score: 3 | Accepted answer
  
  A few orgs who use logging on fairly high volume sites have modified the logging tables to either use MyISAM or InnoDB and have had fairly good success with it. Can you please report back if you adopt this approach and your success with it
  
  
  ---
  
  ### Answer by username_0 on 2015-05-30. Score: 0
  
  Lobo, took your suggestion and converted to InnoDB. We were getting hit with about on failure a month. It has been about 3 weeks, we have not seen a problem. We moved the server to a solid state drive a number of months ago to improve reliability and response time. I don't have any statistics on performance but in general the online system does not write huge amounts of data to the log except when doing a batch operation like a mass mailing,
  
  I would suggest making all new CiviCrm installations use InnoDB to improve reliability which is often much more important then time to log updates.
  
  
  ---
  
  