Tag Splitter Question

Ignition
1

Hello,

We're using a central Ignition gateway for data aggregation from multiple local sites, each with its own Ignition gateway and SQL server. We've set up tag splitters at each site to push data to both a local SQL server and a central SQL server. The initial idea was to have redundancy in case of a loss of connection to the central server. However, I'm wondering if this is necessary since the store-and-forward system should handle connectivity issues.

My questions are:

  1. Does it make sense to maintain local SQL servers for redundancy, or is the store-and-forward system sufficient?
  2. Should we keep the local SQL servers for short-term queries, or is it better to rely solely on the central SQL server?
2

Yes, and yes. You want local access to your data when the WAN is down, and for local charting performance.

Consider using database replication to the central database instead of history splitters. Then configure your remote tag providers in the central gateway to divert history queries to your replica.