We have had a couple of odd issues recently where it appears that we have had multiple records created in a SQL Server database from a single insert query coming from Ignition.
For example, we have a script that retrieves data from a table, and based on the contents of each record, it will create a separate record in another table. In 2 instances recently, we have found 2 records with the exact same timestamp (down to the ms) in the destination table, and we cannot find anything that would have caused the query to run twice on our end. We are using system.db.runPrepUpdate for this insert.
Also, it may be helpful to mention that the timestamp is set by using CURRENT_TIMESTAMP function in SQL Server.
If there is some sort of network disruption between Ignition and SQL Server, is there any chance that the command could be sent twice to SQL Server? I’m just looking for any insight into something I might be missing.