Database table - sqlt_te

Ignition
1

Hi Ignition community,

I have a question regarding database that is linked to Ignition. When we create a database connection there will be several tables created. One of the table name is "sqlt_te". In this table we can see there are column named "tagpaths" and it's corresponding "tagid". The "tagpaths" and the "tagid" will be created when we enable historization in Ignition designer together with it's "created" timestamp.

Let's say there are tags with "retired" timestamps,I believe those tags are no longer historizing or the tags are no longer available in gateway.

I would like to know if it is safe to delete all the rows where the "tagpaths" are retired?

Below is the screenshot.

image

Thank you in advance

2

No, you have to see if any data in the partitions is still using that tag id. When looking for history in a query, Ignition will use all tag id's, including retired ones, that fit the time span and have the desired tag path(s).

If there are no more rows in the partitions with a retired tag id, you can delete it.

3

Hi @pturmel

For example I have three partitions(sqlt_data_1_2026_02, sqlt_data_1_2026_03 and sqlt_data_1_2026_04) at the moment and there is a retired tagid, 123.

The tagid 123 exist in partition sqlt_data_1_2026_02 but not in sqlt_data_1_2026_03 and sqlt_data_1_2026_04. Is it still safe to delete or as long there is a partition with tagid 123 in it, it is not safe to delete it?

Thank you in advance.

4

If you delete the retired tagID and there is data associated with that tagID in any of the retired tables, then when pulling that history up in a trend/report etc... Ignition will not be able to get the data from those partitions.

Rule of thumb... unless you 100% know what you are doing in these tables it is best to just leave it alone.

5

Retired doesn't mean the tag doesn't exist anymore. It just means that specific configuration of the tag is not the current one. If you change anything in the history setup of the tag, the "old" id gets retired a new id gets created. But the old id is still valid for all the history it was "not-retired" for.

Out of curiosity, what are you trying to accomplish?

6

Hi Guys.

Thank you for the replies and it is clear now.

@tgarrison, basically I am just trying to understand the risk, nothing else. :slight_smile:

Regards