Which approach to follow - Tag Historian /Transaction Groups/Tag Event Script and Query Tag/Named Query

[pturmel]

There's no general rule. Tell us what you are trying to do. But these links might help:

SQL Tall/Long vs Wide Table Structure

I am in the process of trying to collect high speed historical data to an MSSQL database. We would like to collect data to set up a predictive maintenance system. We would like to collect information like temperature, vibration, voltage, current, etc. on CNC machines on a per machine cycle/part cycle basis at a 100mS sample rate. We would then like to compare the charts based on machine/part cycle to set thresholds and detect abnormalities before they become breakdowns. We are collecting all…

Organizing SQL tables and named queries efficiently

If you have a bunch of machines, and multiple events to track, is it best to have a transaction group for each event type, and for each machine? I read one guy say if you had a bunch of machines, you wanted to organize all of them into one table. I thought the limitations on SQL were that as a table gets bigger, the queries slow down. So I thought that if my tables are split up, then my tables will be smaller with the same total growth.

Second guessing architecture

I’m currently writing maintenance documentation for what is officially my first Ignition deployment in the wild. The system is a data concentrator that monitors multiple identical machines and writes a consistent set of data to two different DB tables - one table has one row per machine and is updated in real time with various state values. The second table archives other data on the completion of that machines current instruction, and has one row per instruction. There is no UI on this proj…