8.3 Core Historian Implementation

Ignition
1

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
image211×112 6.06 KB

as licenses have already been bought and I cannot buy another one at this time in the project.

2 Likes
2

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

3

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

4

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

1 Like
5

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.

6

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.