0
History.db can become huge with the logs and create issue for backup/restore
i had to face an issue, I could backup from server but could not restore (import) my backup file in a new team.
The only place I could restore this 750mb was in the local app db.
Support said there was an issue with number of records, development team was checking.
I was suspecting the history log becoming huge
So what I did was to purely delete the 2.7Gb history.db locally in the MacOS library.
Then backup again and then I was able to import in a team on the server.
I would recommend from that experience to carefully select the tables having the history set active and to sometimes clean it.
I haven’t dared so far to delete history with the option on the server as it is a productive database.
Any experience like this , another solution ?
Reply
Content aside
- 4 yrs agoLast active
- 356Views