Hello,
We have a historical table that’s growing really fast. It’s only 2 and half months but the data is already at 75GB. Is there a way to compressed the tag historian table data?
From the Ignition side you must check the history scan class for tags, the size of data is too big, means you are storing a lot of variables way to fast.
Anyway, what comes to my mind is to reduce the partition size, seems like you have a 2 months partition. In your case I would try 1 weeks partition for example.
Also enable pruning
The Tag Historian, like in most SCADA packages, offers two key advantages:
- Configuration convenience. Just check a box and the defaults will record your tag. The database tables are structured to accommodate any number of tags in any hierarchy, by storing just one sample from one tag at one timestamp in its own row. (AKA “tall” format.)
- Storage savings for tags that don’t change often (boolean events, perhaps) or normally change very little around an otherwise stable value. The latter depends on a little more configuration, where someone knowledgeable about the process sets an appropriate deadband and possibly a minimum time between samples.
The alternative old-school format is to create tables specifically for groups of tags, and record them together in single rows (AKA “wide” format). In Ignition, this would typically be done with Transaction Groups, part of the SQL Bridge module. For tags that are constantly changing, or must be recorded at constant intervals, wide format is much more space-efficient.
Unfortunately, failing to set deadbands and appropriate intervals for noisy tags will make your Tag Historian record a great deal more data than you likely need. When auditing your tags for appropriate history settings, you should do so in light of Ignition’s analog value compression algorithm.
It seems we’re doing wrong on configuring our tag history.
What we think here is that this tag only stores data on every tag change, is that correct?
If not, can you explain how much data this tag is storing on tag historian table?
and also this is an analog tag (power meter kwh)
Based on your setting it will store new data everytime the value changes 0.01. So of you are doing kwh so you need that resolution? Usually having the dead and too low will end up logging a to more data then you really need.