# Data pruning when no partitioning is configured

**URL:** <https://forum.inductiveautomation.com/t/data-pruning-when-no-partitioning-is-configured/37936>\
**Category:** Ignition\
**Tags:** ignition79\
**Created:** [August 20, 2020, 9:21am UTC](https://forum.inductiveautomation.com/t/data-pruning-when-no-partitioning-is-configured/37936 "2020-08-20T09:21:31Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![pgmo](https://avatars.discourse-cdn.com/v4/letter/p/d07c76/32.png) [@pgmo](https://forum.inductiveautomation.com/u/pgmo)\
**Post date:** [August 20, 2020, 9:21am UTC](https://forum.inductiveautomation.com/t/data-pruning-when-no-partitioning-is-configured/37936/1 "2020-08-20T09:21:31Z")

</div>

In one of my projects I’ve enabled **no Data partitioning**. Nontheless **I need Data pruning**. In the hints for _Data pruning_ I read:  
 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/a/e/aef68b150e193f8e79abea4b0f344556560c32e3.png)  
Am I right if I say that in my case, i.e. without any partitioning enabled, I will have no data pruning at all? In this case is it safe just to delete older data in the **sqlt\_data\_1\_xxxxxx** table?  
 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/d/d/dd649ee053d2e63c58d140d1da9fd678153a3df7.png)  
Or do I have to deal with  
 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/d/e/de6e659a69b5c634dab6958d1daa1092f3966846.png)  
as well?

Thanks in davance, regards

---

<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:** [August 20, 2020, 2:30pm UTC](https://forum.inductiveautomation.com/t/data-pruning-when-no-partitioning-is-configured/37936/2 "2020-08-20T14:30:13Z")

</div>

If you have a single partition, it’s possible to directly delete old data yourself. You will probably want to update the time range represented in `sqlth_partitions` at the same time - that will prevent the historian issuing a query for data that’s not actually there, but even without that, things should mostly just work.

Disclaimer being that although I’m pretty versed in the historian I haven’t actually tried this myself, so I’m not committing to a 100% guarantee.

---

<div class="post-metadata">

**Author:** ![pgmo](https://avatars.discourse-cdn.com/v4/letter/p/d07c76/32.png) [@pgmo](https://forum.inductiveautomation.com/u/pgmo)\
**Post date:** [August 22, 2020, 10:20am UTC](https://forum.inductiveautomation.com/t/data-pruning-when-no-partitioning-is-configured/37936/3 "2020-08-22T10:20:41Z")

</div>

Ok, many thanks Mr PGriffith, I will give it a try.

Regards
