# Multiple rows with different timestamp in sqlth\_partitions **URL:** \ **Category:** Ignition\ **Created:** [June 2, 2023, 4:22am UTC](https://forum.inductiveautomation.com/t/multiple-rows-with-different-timestamp-in-sqlth-partitions/74469 "2023-06-02T04:22:14Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![Dharani\_T](https://avatars.discourse-cdn.com/v4/letter/d/bc8723/32.png) [@Dharani\_T](https://forum.inductiveautomation.com/u/Dharani_T)\ **Post date:** [June 2, 2023, 4:22am UTC](https://forum.inductiveautomation.com/t/multiple-rows-with-different-timestamp-in-sqlth-partitions/74469/1 "2023-06-02T04:22:14Z")
Hi, I could see multiple entries with same pname in sqlth\_partitions but with different time stamp. Setup: ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/d/4/d483dee846d2091798b060407786cd326e2c981e.png) Results: ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/8/4/8444b6c7fb9cd65ab7f9c92443b831d25b1c7710.png) If this is a problem, what should i have to modify? ---
**Author:** ![justinedwards.jle](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/justinedwards.jle/32/37854_2.png) [@justinedwards.jle](https://forum.inductiveautomation.com/u/justinedwards.jle)\ **Post date:** [June 3, 2023, 9:07am UTC](https://forum.inductiveautomation.com/t/multiple-rows-with-different-timestamp-in-sqlth-partitions/74469/2 "2023-06-03T09:07:49Z")
so this isn't causing an observable issue... You are just wanting to know if this is normal? ---
**Author:** ![Dharani\_T](https://avatars.discourse-cdn.com/v4/letter/d/bc8723/32.png) [@Dharani\_T](https://forum.inductiveautomation.com/u/Dharani_T)\ **Post date:** [June 3, 2023, 9:19am UTC](https://forum.inductiveautomation.com/t/multiple-rows-with-different-timestamp-in-sqlth-partitions/74469/3 "2023-06-03T09:19:35Z")
I just know whether this is normal or we have to take any corrective measures. ---
**Author:** ![Transistor](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/transistor/32/3380_2.png) [@Transistor](https://forum.inductiveautomation.com/u/Transistor)\ **Post date:** [June 3, 2023, 9:30am UTC](https://forum.inductiveautomation.com/t/multiple-rows-with-different-timestamp-in-sqlth-partitions/74469/4 "2023-06-03T09:30:27Z")
Where is the **pname** list coming from? ---
**Author:** ![Dharani\_T](https://avatars.discourse-cdn.com/v4/letter/d/bc8723/32.png) [@Dharani\_T](https://forum.inductiveautomation.com/u/Dharani_T)\ **Post date:** [June 3, 2023, 9:31am UTC](https://forum.inductiveautomation.com/t/multiple-rows-with-different-timestamp-in-sqlth-partitions/74469/5 "2023-06-03T09:31:33Z")
> [@Dharani\_T](#): > > sqlth\_partitions From sqlth\_partitions table , and i have used biweekly parition ---
**Author:** ![justinedwards.jle](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/justinedwards.jle/32/37854_2.png) [@justinedwards.jle](https://forum.inductiveautomation.com/u/justinedwards.jle)\ **Post date:** [June 5, 2023, 12:23pm UTC](https://forum.inductiveautomation.com/t/multiple-rows-with-different-timestamp-in-sqlth-partitions/74469/6 "2023-06-05T12:23:11Z")
If pname is a primary key, the database shouldn't be allowing that. ---
**Author:** ![Dharani\_T](https://avatars.discourse-cdn.com/v4/letter/d/bc8723/32.png) [@Dharani\_T](https://forum.inductiveautomation.com/u/Dharani_T)\ **Post date:** [June 5, 2023, 12:25pm UTC](https://forum.inductiveautomation.com/t/multiple-rows-with-different-timestamp-in-sqlth-partitions/74469/7 "2023-06-05T12:25:42Z")
This table will be created automatically right? it do not have a primary key ---
**Author:** ![lrose](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/lrose/32/62724_2.png) [@lrose](https://forum.inductiveautomation.com/u/lrose)\ **Post date:** [June 5, 2023, 12:30pm UTC](https://forum.inductiveautomation.com/t/multiple-rows-with-different-timestamp-in-sqlth-partitions/74469/8 "2023-06-05T12:30:14Z")
This is the partitions table. Ignition uses it to cross partition boundaries when using Ignitions provided historical functions. Are the `start_time` and `end_time` columns also identical? Have you been making adjustments to your history settings? The table is created and maintained by Ignition. Changing it manually can break things. ---
**Author:** ![Dharani\_T](https://avatars.discourse-cdn.com/v4/letter/d/bc8723/32.png) [@Dharani\_T](https://forum.inductiveautomation.com/u/Dharani_T)\ **Post date:** [June 5, 2023, 12:31pm UTC](https://forum.inductiveautomation.com/t/multiple-rows-with-different-timestamp-in-sqlth-partitions/74469/9 "2023-06-05T12:31:12Z")
start\_time and end\_time are not identical. ---
**Author:** ![lrose](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/lrose/32/62724_2.png) [@lrose](https://forum.inductiveautomation.com/u/lrose)\ **Post date:** [June 5, 2023, 12:32pm UTC](https://forum.inductiveautomation.com/t/multiple-rows-with-different-timestamp-in-sqlth-partitions/74469/10 "2023-06-05T12:32:46Z")
I would not be concerned. If Ignition isn't complaining and your not observing any issues with gaps in data or unexpected returns, then probably best to assume all is well. Otherwise I would call support and have them look through it and verify that all is well.