# Historical Data can not be stored in the SQL Historian

**URL:** <https://forum.inductiveautomation.com/t/historical-data-can-not-be-stored-in-the-sql-historian/115312>\
**Category:** Ignition\
**Tags:** perspective\
**Created:** [April 29, 2026, 7:34pm UTC](https://forum.inductiveautomation.com/t/historical-data-can-not-be-stored-in-the-sql-historian/115312 "2026-04-29T19:34:27Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![andrei.veremeenko](https://avatars.discourse-cdn.com/v4/letter/a/a87d85/32.png) [@andrei.veremeenko](https://forum.inductiveautomation.com/u/andrei.veremeenko)\
**Post date:** [April 29, 2026, 7:34pm UTC](https://forum.inductiveautomation.com/t/historical-data-can-not-be-stored-in-the-sql-historian/115312/1 "2026-04-29T19:34:27Z")

</div>

Hello everyone,

I am sending some data from the RTAC to Ignition over DNP3 Protocol with the idea of displaying current and historical values using the Power Chart Component. I previously had SQL Historian running on the MySQL Server and did not have any issues, but this time I have configured SQL Historian that uses Microsoft SQL Server, and in the Diagnostics Logs, I am receiving the following error:

`TagHistoryDatasourceSink: Unsupported persistent flavor received by history sink, data will not be stored: DefaultPersistentFlavor{signature='historical_metadata', systemType=Tag History}`

With that in mind, I still tried to add some points on the Power Chart in the Designer and, initially, nothing was shown, but they appeared in the next 5 minutes. Please take a look at the screenshot below:

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/e/7/e7e5ded87399e4974ee7d564a62daefc72693b0c.png)

However, I was not able to add points while running session in the browser, even though the chart identified three points that I was trying to add. Please refer to the screenshot below.

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/3/a/3adc822f1251934ff46eca285766a8c3d075442a.png)

Additionally, I tried using the Core Historian instead and experienced the same behavior.

So, I am now wondering whether it has something to do with the data I am sending from the RTAC or it might be something else. Let me know if you require some additional information.

Thanks in advance,

Andrei
