We’re currently capturing the data of one of our tags with tag historian and due to having people in our business who aren’t going to have access to the same network our ignition server is running on, we want consume the data from tag historian with another tool. However, due to the automatic partitioning of the data written by tag historian, it makes what should be a quite simple job a lot harder.
I wondered if there was anyway to prevent tag historian from partitioning the data?
No idea how I missed that.