Tag historian Vs transaction groups when storing data for OEE system

[pturmel]

Start here:

SQL Tall/Long vs Wide Table Structure

I generally make tables wide enough to permit related values to share a row in a table with a single timestamp column. This is the classic transaction group. If multiple entities share that specific structure, I include a column to indicate which entity to minimize the proliferation of tables. That would be the block transaction group, though I don’t usually use it – I prefer to trigger individual rows as needed. Both of these approaches are extremely friendly to external data analysis, but …

More discussions:

https://forum.inductiveautomation.com/search?q=db%20tall%20wide%20order%3Alatest

Also, keep in mind that anything that can be done with a transaction group can be done with scripted DB calls. This is particularly helpful when you need something for every instance of a UDT.

(But don't do SQL insert/update calls directly from a tag's valueChange event--use the Store and Forward versions.)