# Multiple databases in single history provider/store

**URL:** <https://forum.inductiveautomation.com/t/multiple-databases-in-single-history-provider-store/82732>\
**Category:** Ignition\
**Tags:** database, ignition81\
**Created:** [December 5, 2023, 5:29pm UTC](https://forum.inductiveautomation.com/t/multiple-databases-in-single-history-provider-store/82732 "2023-12-05T17:29:04Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Connor\_Sims](https://avatars.discourse-cdn.com/v4/letter/c/c77e96/32.png) [@Connor\_Sims](https://forum.inductiveautomation.com/u/Connor_Sims)\
**Post date:** [December 5, 2023, 5:29pm UTC](https://forum.inductiveautomation.com/t/multiple-databases-in-single-history-provider-store/82732/1 "2023-12-05T17:29:04Z")

</div>

The [Tag Properties](https://docs.inductiveautomation.com/display/DOC81/Tag+Properties) document indicates "A particular Tag can only target one history store."

Can this one history store be multiple mysql databases on the same server? Or, must we specify one particular mysql database? . (For my example below, I wonder if it is possible to point a database connection to **jdbc:mysql://server2.corp.company.com:3306** instead of **jdbc:mysql://server2.corp.company.com:3306/SCADA2)**

For simplicity, let's assume I have a single realtime provider (the SCADA database on server1). I know I can use a second, separate source as a history provider (the SCADA2 database on server2).

What I wonder is whether the SCADA2 database on server2 can actually be 12 separate databases partitioned by month, SCADA01, SCADA02, etc - & if pointing to the whole server in the database connection, as opposed to a specific database, could still work.

Thanks for any advice.

---

<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:** [December 5, 2023, 6:02pm UTC](https://forum.inductiveautomation.com/t/multiple-databases-in-single-history-provider-store/82732/2 "2023-12-05T18:02:19Z")

</div>

For the sake of answering your question, I'll point you to the [Tag History Splitter](https://docs.inductiveautomation.com/display/DOC81/Tag+History+Providers#TagHistoryProviders-TagHistorySplitter) - you can connect a particular tag to only one history provider, but that history provider doesn't necessarily have to map to a single database.

However, I really have to ask what benefit you think you would derive from your proposed architecture.

---

<div class="post-metadata">

**Author:** ![Connor\_Sims](https://avatars.discourse-cdn.com/v4/letter/c/c77e96/32.png) [@Connor\_Sims](https://forum.inductiveautomation.com/u/Connor_Sims)\
**Post date:** [December 6, 2023, 5:13pm UTC](https://forum.inductiveautomation.com/t/multiple-databases-in-single-history-provider-store/82732/3 "2023-12-06T17:13:21Z")

</div>

Thank you, this answers my question & confirms I'll take another approach. & this proposed architecture was a an attempt to leverage an already existing data architecture used for reporting, which is entirely customized.