# Ignition Deleting Tag History

**URL:** <https://forum.inductiveautomation.com/t/ignition-deleting-tag-history/93387>\
**Category:** Ignition\
**Created:** [July 18, 2024, 10:41am UTC](https://forum.inductiveautomation.com/t/ignition-deleting-tag-history/93387 "2024-07-18T10:41:44Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Kieran\_Lynn](https://avatars.discourse-cdn.com/v4/letter/k/c77e96/32.png) [@Kieran\_Lynn](https://forum.inductiveautomation.com/u/Kieran_Lynn)\
**Post date:** [July 18, 2024, 10:41am UTC](https://forum.inductiveautomation.com/t/ignition-deleting-tag-history/93387/1 "2024-07-18T10:41:44Z")

</div>

At some point, tag history tables were deleted manually (due to memory) from our SQL database. Pruning was then set up on a monthly basis. However, in the gateway logs, errors continue to populate with the following error message:

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/6/2/62196d2994b7618fd724453aa7ab566771e43fab.png)  
I believe deleting the corresponding row from the sqlth\_partitions table will remove these error messages from occuring.

Does anyone know if doing so will cause any problems? Thanks

---

<div class="post-metadata">

**Author:** ![Hayden\_Watson](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/hayden_watson/32/48792_2.png) [@Hayden\_Watson](https://forum.inductiveautomation.com/u/Hayden_Watson)\
**Post date:** [July 18, 2024, 11:27am UTC](https://forum.inductiveautomation.com/t/ignition-deleting-tag-history/93387/2 "2024-07-18T11:27:36Z")

</div>

> **[Ignition Database Table Reference | Ignition User Manual](https://www.docs.inductiveautomation.com/docs/8.1/appendix/reference-pages/ignition-database-table-reference)**
>
> Ignition has a lot of systems built-in that will query the database automatically without requiring you to build a query. These systems automatically create the necessary tables in the database, insert the relevant data, and even query it back out...

Might want to check the `sqlth_partitions` table and remove the partitions you've deleted.
