# Historian writing null values to DB

**URL:** <https://forum.inductiveautomation.com/t/historian-writing-null-values-to-db/74976>\
**Category:** Ignition\
**Tags:** perspective\
**Created:** [June 13, 2023, 7:15pm UTC](https://forum.inductiveautomation.com/t/historian-writing-null-values-to-db/74976 "2023-06-13T19:15:05Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![David\_Duquette](https://avatars.discourse-cdn.com/v4/letter/d/7ab992/32.png) [@David\_Duquette](https://forum.inductiveautomation.com/u/David_Duquette)\
**Post date:** [June 14, 2023, 11:00am UTC](https://forum.inductiveautomation.com/t/historian-writing-null-values-to-db/74976/4 "2023-06-14T11:00:46Z")

</div>

I found the solution in the forum.

# [Strange behavior with partitioned historian data tables](https://forum.inductiveautomation.com/t/strange-behavior-with-partitioned-historian-data-tables/15964)

I originally had the project running on my laptop before transferring it over to a different PC. A second table was created. "sqlt\_data\_3\_2023\_06". I removed all the tables and restarted the gateway. Everything is working again.

I didn't need the information that was recorded so this wasn't a big deal taking this approach but it would be nice to have a better a solution so the data could be saved if I were to ever run into something similar in the future. Is it as simple as deleting the two extra entries in "sqlth\_drv"?

---

_[View the full topic](https://forum.inductiveautomation.com/t/historian-writing-null-values-to-db/74976)._