# 8.3 Core Historian Implementation

**URL:** <https://forum.inductiveautomation.com/t/8-3-core-historian-implementation/111798>\
**Category:** Ignition\
**Created:** [October 29, 2025, 7:45pm UTC](https://forum.inductiveautomation.com/t/8-3-core-historian-implementation/111798 "2025-10-29T19:45:43Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jacob\_Winter](https://avatars.discourse-cdn.com/v4/letter/j/5fc32e/32.png) [@Jacob\_Winter](https://forum.inductiveautomation.com/u/Jacob_Winter)\
**Post date:** [October 29, 2025, 7:45pm UTC](https://forum.inductiveautomation.com/t/8-3-core-historian-implementation/111798/1 "2025-10-29T19:45:44Z")

</div>

Hello,

I am implementing a new install of Ignition 8.3 and have a few questions about the new core historian.

If there is no current way to implement the Core Historian on a remote server, are you able to utilize a Historian Splitter to still use a conventional remote DB server? If it is possible, is this best practice and/or will there be any challenges? Like many others in the forum, I am interested in the capabilities of the core historian, but I am hesitant to have the gateway and DB on the same server. I am disappointed that there was not more documentation to go down this path,

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/d/2/d27e32983e22613bc07b2fc3492562b7b3cbccce.png)  
as licenses have already been bought and I cannot buy another one at this time in the project.

---

<div class="post-metadata">

**Author:** ![Kyle\_Chase](https://avatars.discourse-cdn.com/v4/letter/k/9de0a6/32.png) [@Kyle\_Chase](https://forum.inductiveautomation.com/u/Kyle_Chase)\
**Post date:** [October 30, 2025, 2:03am UTC](https://forum.inductiveautomation.com/t/8-3-core-historian-implementation/111798/2 "2025-10-30T02:03:10Z")

</div>

The Core Historian works just fine on a remote server. Set up a remote historian and you re good to go.

---

<div class="post-metadata">

**Author:** ![Jacob\_Winter](https://avatars.discourse-cdn.com/v4/letter/j/5fc32e/32.png) [@Jacob\_Winter](https://forum.inductiveautomation.com/u/Jacob_Winter)\
**Post date:** [October 30, 2025, 5:20pm UTC](https://forum.inductiveautomation.com/t/8-3-core-historian-implementation/111798/3 "2025-10-30T17:20:31Z")

</div>

@Kyle_Chase Don’t you need another gateway license in order for the core historian to be on a remote server?

---

<div class="post-metadata">

**Author:** ![DSI600](https://avatars.discourse-cdn.com/v4/letter/d/ad7895/32.png) [@DSI600](https://forum.inductiveautomation.com/u/DSI600)\
**Post date:** [October 30, 2025, 7:39pm UTC](https://forum.inductiveautomation.com/t/8-3-core-historian-implementation/111798/4 "2025-10-30T19:39:50Z")

</div>

Yes - Only way to have a remote historian at the moment is the SQL Tag HIstorian or a 3rd party historian.

---

<div class="post-metadata">

**Author:** ![Kyle.Chase](https://avatars.discourse-cdn.com/v4/letter/k/3bc359/32.png) [@Kyle.Chase](https://forum.inductiveautomation.com/u/Kyle.Chase)\
**Post date:** [October 31, 2025, 8:46pm UTC](https://forum.inductiveautomation.com/t/8-3-core-historian-implementation/111798/5 "2025-10-31T20:46:19Z")

</div>

Yes, you will need another license.

Core Historian works just fine on a remote gateway. You do not need a SQL Historian or a 3rd party historian.

---

<div class="post-metadata">

**Author:** ![DSI600](https://avatars.discourse-cdn.com/v4/letter/d/ad7895/32.png) [@DSI600](https://forum.inductiveautomation.com/u/DSI600)\
**Post date:** [November 1, 2025, 12:56pm UTC](https://forum.inductiveautomation.com/t/8-3-core-historian-implementation/111798/6 "2025-11-01T12:56:53Z")

</div>

That was my point though. The OP said he already bought licenses and can’t buy another license. So the only way for a ‘remote’ historian is to not use the core historian.