Unable to show tags in power chart

I think it may be a SQL issue but unsure how to troubleshoot. My OPC tags weren't working so I went back to as simple as possible. A memory tag in the root tag provider folder and it still gives me an error in the power chart of "No Trend Data Source (Bad_NotFound)

image

My database is connected and showing valid. As well when the power chart is live in perspective it's showing queries.
image

However I am getting errors in my logs.

What I have noticed is:

  1. In the power chart after I added the tag, if I select edit the path is all lower case, but part of my server name is capitals, if I edit the path to include those capitals the power chart error slightly changes and removes the (Bad_NotFound) part but it still says No Trend Data Source available.

  2. In SQLExpress I see tables created from the historian, the drv table looks correct but I wonder if the scinfo and other tables are actually working properly?

sqlth_drv

sqlth_scinfo

sqlth_sce is empty

sqlt_data_1_2025_04

Run a SQL query directly on the database to verify if any data is being stored for the time range selected on the Power Chart.

If you just created the tag or enabled history, the selected time range in the Power Chart might not include any data yet. Try expanding the range to make sure.

So I see the tag created within sqlth_te as soon as I add it and enable history.

image

However in sqlt_data_1_2025_04 I am not seeing any data appear with the query below. Even after changing the value a few times and waiting an hour. So it appears it's not writing the history in.

SELECT TOP 100 *
FROM [test].[dbo].[sqlth_1_data]
WHERE tagid = 985;

Returns nothing.

Edit: I did separately create a transaction group that records this tag and noticed that does correctly write into the group_table. And if I add a DB_table_historian into my history providers I can pull that into the power chart and it works. But my understanding is that I should be able to pull the tag without going with a transaction group? Or am I wrong thinking in that.

Correct.

The sqlth_sce table should definitely not be empty. I would also expect to see more in sqlth_scinfo.

I would recommend that you call into support so they can look over your shoulder.

So I found the data, I didn't realize the tagid changed when I switched the tag history from on change to periodic and back when testing.

The data is writing correctly into sqlt_data_1_2025_04

I also found the data is writing into sqlt_data_1_2025_04 and not into sqlth_1_data if that matters? I did disable/enable partitioning setting in the tag history provider at one point during testing so I'm assuming the second table was created from that. Do I need to remove sqlth_1_data? Or it shouldn't matter?

It should not matter.

Any changes that you make to the tag, can and often do result in a new Tag ID. However, that shouldn't matter as the history system looks up the ID by tag path.

I changed the sample mode from On Change to Tag Group and put the Default historical group. Doing so did create corresponding entries in sqlth_scinfo and sqlth_sce now.

Huge props to Ignition support was able to resolve it quickly with them. The issue was the drv table was missing an entry and sceinfo changed.

1 Like