Answers.Body: <p>Yes it's just for logging - you can truncate. If you think you might need the logs later you can back up just that table first and store it somewhere.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2023-03-13T04:29:14.387Z
Answers.Text: ok, thanks very much!
Answers.UserDisplayName: user3016811
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2023-03-13T00:46:23.120Z
Answers.LastActivityDate: 2023-03-13T00:46:23.120Z
Answers.UserDisplayName: Demerit
Body: <p>Dealing with an old 4.7 site on Drupal 7, has a huge (21 million row) log_civicrm_group table which I can see has been flagged as a bug in later versions - am I safe to empty/truncate that table?</p>
  <p>Thanks!</p>
  
Tags: <logs>
Title: Safe to empty log_civicrm_group? 4.7
ThreadText: # Safe to empty log_civicrm_group? 4.7
  
  (Asked by: username_0 on 2023-03-12)
  
  Dealing with an old 4.7 site on Drupal 7, has a huge (21 million row) log\_civicrm\_group table which I can see has been flagged as a bug in later versions - am I safe to empty/truncate that table?
  
  Thanks!
  
  **Tags:** logs
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2023-03-13. Score: 1 | Accepted answer
  
  Yes it's just for logging - you can truncate. If you think you might need the logs later you can back up just that table first and store it somewhere.
  
  > **Comments:**
  > **username_0**: ok, thanks very much!  
  
  ---
  
  