# Multiple Data Pruning Policy for One Database Connection

**URL:** <https://forum.inductiveautomation.com/t/multiple-data-pruning-policy-for-one-database-connection/106529>\
**Category:** Ignition\
**Tags:** database\
**Created:** [May 21, 2025, 8:15pm UTC](https://forum.inductiveautomation.com/t/multiple-data-pruning-policy-for-one-database-connection/106529 "2025-05-21T20:15:19Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![jimmy.ruan](https://avatars.discourse-cdn.com/v4/letter/j/7ea924/32.png) [@jimmy.ruan](https://forum.inductiveautomation.com/u/jimmy.ruan)\
**Post date:** [May 21, 2025, 8:15pm UTC](https://forum.inductiveautomation.com/t/multiple-data-pruning-policy-for-one-database-connection/106529/1 "2025-05-21T20:15:19Z")

</div>

We have an Ignition setup where some tags whose history we want to keep for 3 month and others for 3 years - in the same database.

Is it possible to set up multiple tag history provider with different data pruning configurations for the same database? If so, how?

System: Ignition 8.1.43  
Database: Oracle 19

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [May 22, 2025, 12:52pm UTC](https://forum.inductiveautomation.com/t/multiple-data-pruning-policy-for-one-database-connection/106529/2 "2025-05-22T12:52:21Z")

</div>

You can point multiple Ignition database connections at the same real database, yielding separate storage providers with independent settings. Ignition will mark metadata in the real DB with the Ignition connection name and produce separate data partition tables with the different lifetimes.