# Ignition creates new table every month in MySQL database

**URL:** <https://forum.inductiveautomation.com/t/ignition-creates-new-table-every-month-in-mysql-database/80091>\
**Category:** Ignition\
**Tags:** ignition81\
**Created:** [October 5, 2023, 4:54pm UTC](https://forum.inductiveautomation.com/t/ignition-creates-new-table-every-month-in-mysql-database/80091 "2023-10-05T16:54:40Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Oscar\_Aliaga](https://avatars.discourse-cdn.com/v4/letter/o/3ab097/32.png) [@Oscar\_Aliaga](https://forum.inductiveautomation.com/u/Oscar_Aliaga)\
**Post date:** [October 5, 2023, 4:54pm UTC](https://forum.inductiveautomation.com/t/ignition-creates-new-table-every-month-in-mysql-database/80091/1 "2023-10-05T16:54:40Z")

</div>

Good day with everyone, I am working on a project that involves ignition and mysql workbench, however, since it is a new month, ignition generates a new table of the month, leaving the other data behind, how could I prevent this from happening and all the data is only stored in a single table, your support please.

---

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [October 5, 2023, 4:57pm UTC](https://forum.inductiveautomation.com/t/ignition-creates-new-table-every-month-in-mysql-database/80091/2 "2023-10-05T16:57:32Z")

</div>

You can disable partitioning on your history provider:  
[https://docs.inductiveautomation.com/display/DOC81/Tag+History+Providers#TagHistoryProviders-DatasourceHistoryProvidersSettings](https://docs.inductiveautomation.com/display/DOC81/Tag+History+Providers#TagHistoryProviders-DatasourceHistoryProvidersSettings)

Be warned that this will make a table that grows infinitely; pruning of old historical data operates on the entire table, so if you disable partitioning _Ignition_ will never go in and delete old historical data for you, which can bog down your DB over time.

---

<div class="post-metadata">

**Author:** ![Transistor](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/transistor/32/3380_2.png) [@Transistor](https://forum.inductiveautomation.com/u/Transistor)\
**Post date:** [October 5, 2023, 5:11pm UTC](https://forum.inductiveautomation.com/t/ignition-creates-new-table-every-month-in-mysql-database/80091/3 "2023-10-05T17:11:43Z")

</div>

> [@Oscar\_Aliaga](#):
>
> Ignition generates a new table of the month ...

Ignition only does this on the history provider. It means that when you use Ignition's built-in history queries that they run much more quickly since they only have to query the months (or whatever time periods have been configured) between the start and end dates of the query.

If you are writing queries to read from the historian tables then I suspect that there is something wrong with your project structure or your understanding of how the historian works.