# Mautic DB Huge - Events & Import History - what can be deleted

**URL:** https://forum.mautic.org/t/mautic-db-huge-events-import-history-what-can-be-deleted/16336
**Category:** Product Support
**Created:** [September 29, 2020, 4:03pm UTC](https://forum.mautic.org/t/mautic-db-huge-events-import-history-what-can-be-deleted/16336 "2020-09-29T16:03:37Z")
**Posts on this page:** 1
**Showing post:** 3

<div class="post-metadata">

### Author: ![joeyk](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/joeyk/32/11164_2.png) [@joeyk](https://forum.mautic.org/u/joeyk)
#### Post date: [October 2, 2020, 7:04pm UTC](https://forum.mautic.org/t/mautic-db-huge-events-import-history-what-can-be-deleted/16336/3 "2020-10-02T19:04:11Z")

</div>

This is a very hard question. I have the answer, but you not gonna like it.

Will you need tracking data?

- If not, why to use Mautic?
- If yes you’ll need to scale this up.  
More info: [Login to Meetup | Meetup](https://www.meetup.com/Mautic-Meetup-Lagos/events/272511292/)

Or check this:

> [@Delete old rows from email\_stats table without breaking front-end](https://forum.mautic.org/t/delete-old-rows-from-email-stats-table-without-breaking-front-end/11201/3):
>
> Hi Ruth: Thanks so much for your reply. I’ve reviewed the issue as reported on GitHub. I think I’ll use the SQL Update statements as provided in that issue till hopefully a future release addresses the issue. I think any implementation of size makes it quite costly to run given the disk space requirements to handle how it presently grows the email\_stats table. I would imagine the [mautic.com](http://mautic.com) folks are experiencing some pain on this issue, ya? Thanks again! Bob H.

---

_[View the full topic](https://forum.mautic.org/t/mautic-db-huge-events-import-history-what-can-be-deleted/16336)._
