# Store and forward - old data from 2014 **URL:** \ **Category:** Ignition\ **Tags:** ignition83, database\ **Created:** [June 7, 2026, 11:53am UTC](https://forum.inductiveautomation.com/t/store-and-forward-old-data-from-2014/115878 "2026-06-07T11:53:41Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![vahelduvool](https://avatars.discourse-cdn.com/v4/letter/v/ea666f/32.png) [@vahelduvool](https://forum.inductiveautomation.com/u/vahelduvool)\ **Post date:** [June 7, 2026, 11:53am UTC](https://forum.inductiveautomation.com/t/store-and-forward-old-data-from-2014/115878/1 "2026-06-07T11:53:41Z")
I have problem where old data is popping up in database table. I think tag values are right but time stamps are way in the past. I have managed to pinpoint issue in database, table with name "sqlt\_data\_1\_20140407". In there I can see new data showing up but with old timestamps. In the picture I cleared table before and new data is showing. If I delete the table then store and forward QUARANTINED COUNT will rise about 35 000 in 24h. And I think that´s why ignition has been restarting after few days. What do I need to stop this from happening? ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/3/8/38f9966d2ecbee5e8ce2874eae2c2414586a3dfd.png) ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [June 7, 2026, 12:01pm UTC](https://forum.inductiveautomation.com/t/store-and-forward-old-data-from-2014/115878/2 "2026-06-07T12:01:25Z")
Double-check your PLC clocks where you are using PLC OPC servers. They **must** be correct. ---
**Author:** ![vahelduvool](https://avatars.discourse-cdn.com/v4/letter/v/ea666f/32.png) [@vahelduvool](https://forum.inductiveautomation.com/u/vahelduvool)\ **Post date:** [June 7, 2026, 12:10pm UTC](https://forum.inductiveautomation.com/t/store-and-forward-old-data-from-2014/115878/3 "2026-06-07T12:10:54Z")
I think that was issue. Clock where indeed in 2014 era. How did You know it was to do with OPC servers and its time? ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/0/2/02fe5ba835ad21d64d7a3840fc1a17081a4d34bd.png) ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [June 7, 2026, 12:35pm UTC](https://forum.inductiveautomation.com/t/store-and-forward-old-data-from-2014/115878/4 "2026-06-07T12:35:03Z")
Common problem. OPC **requires** accurate timestamps and Ignition trusts the timestamps from OPC servers. If a few minutes off, this shows up in realtime trends. It is a best practice to synchronize your PLCs with good time sources. I recommend the Time Machines TM2000B, which has both PTP and NTP support. ---
**Author:** ![Chris\_Bingham](https://avatars.discourse-cdn.com/v4/letter/c/e5b9ba/32.png) [@Chris\_Bingham](https://forum.inductiveautomation.com/u/Chris_Bingham)\ **Post date:** [June 8, 2026, 6:27pm UTC](https://forum.inductiveautomation.com/t/store-and-forward-old-data-from-2014/115878/5 "2026-06-08T18:27:32Z")
They added a new property in 8.3.1: "Timestamp Source" w/ description "The source to use for timestamps in values from this connection". > **[Advanced​ - OPC UA Connections | Ignition User Manual](https://www.docs.inductiveautomation.com/docs/8.3/ignition-modules/opc-ua/opc-ua-connections#advanced)** > > The OPC Connections page displays all currently configured OPC (both UA and DA) connections, as well as their status. If any are faulted, you can click the red faulted status to get an error message popup with a full description of the error. | OPC... I have not used it, so I'm not sure if selecting "IGNITION" option would be another solution to your issue.