# Historian rows replicated in sqlth\_partitions

**URL:** <https://forum.inductiveautomation.com/t/historian-rows-replicated-in-sqlth-partitions/80220>\
**Category:** Ignition\
**Created:** [October 9, 2023, 6:35pm UTC](https://forum.inductiveautomation.com/t/historian-rows-replicated-in-sqlth-partitions/80220 "2023-10-09T18:35:33Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![indra.biswas](https://avatars.discourse-cdn.com/v4/letter/i/3bc359/32.png) [@indra.biswas](https://forum.inductiveautomation.com/u/indra.biswas)\
**Post date:** [October 9, 2023, 6:35pm UTC](https://forum.inductiveautomation.com/t/historian-rows-replicated-in-sqlth-partitions/80220/1 "2023-10-09T18:35:33Z")

</div>

Why are there duplicate rows being created in sqlth\_partitions. They have the exact same timestamps. I tried updating the duplicate entries, but somehow in the background Ignition keeps generating a new duplicate all the time. Seems like a bug

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/9/4/94cdd3f28de194056993e2e9e8d6744e3a9877b8.png)

---

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [October 9, 2023, 6:40pm UTC](https://forum.inductiveautomation.com/t/historian-rows-replicated-in-sqlth-partitions/80220/2 "2023-10-09T18:40:29Z")

</div>

What does your `sqlth_drv` table look like? Did someone restore a production .gwbk, non-disabled, on another machine in the network with access to the production DB?

---

<div class="post-metadata">

**Author:** ![indra.biswas](https://avatars.discourse-cdn.com/v4/letter/i/3bc359/32.png) [@indra.biswas](https://forum.inductiveautomation.com/u/indra.biswas)\
**Post date:** [October 9, 2023, 6:42pm UTC](https://forum.inductiveautomation.com/t/historian-rows-replicated-in-sqlth-partitions/80220/3 "2023-10-09T18:42:29Z")

</div>

theres two entries in there as well

I don't believe there was any restoration  
 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/1/7/171d69599ed8be08ef39d3b39ac41685f555838e.png)

---

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [October 9, 2023, 6:47pm UTC](https://forum.inductiveautomation.com/t/historian-rows-replicated-in-sqlth-partitions/80220/4 "2023-10-09T18:47:28Z")

</div>

> [@indra.biswas](#):
>
> I don't believe there was any restoration

I don't believe you 🙂

Your DRV table looks correct, which eliminates one possible source of partition confusion. Check your database logs to see the incoming IP(s) that are creating these tables. If they're both the same source gateway I'll be very surprised.

---

<div class="post-metadata">

**Author:** ![MMaynard](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/mmaynard/32/3366_2.png) [@MMaynard](https://forum.inductiveautomation.com/u/MMaynard)\
**Post date:** [October 9, 2023, 7:23pm UTC](https://forum.inductiveautomation.com/t/historian-rows-replicated-in-sqlth-partitions/80220/5 "2023-10-09T19:23:42Z")

</div>

@paul-griffith just a heads up but we have an open ticket with a bug report on this and have been told it won't be fixed until 8.3 ☹  
It is caused by records coming in out of order is what we have been told.  
IGN-2130  
And ticket #92437

I have a custom SQL Function that I use to fix the duplicates for now, but it is a pain.