We are using Ignition 7.2.9 to monitor production work cells in a medical device MFG factory. We have developed our own version of OEE monitoring using PLC logic, Ignition scripting and MSSQL 2005 Stored Procedures.
All INSERTS and UPDATES are performed by MSSQL Stored Procedures that are triggered by Ignition Transaction Groups.
We recently moved our MSSQL records and Stored Procedures from our Dept. database where they had run well for 1 year to our FDA validated plant database. From May 29 to June 22 over 700,000 duplicate records were unintentionally created. There were some DB anolomies coincident with the beginning of the duplicate records. Multiple old DB tables were merged into a single table and the table identity was reseeded on May 29th. Neither the DBA or I can see how reseeding the ID would create duplicate records over the course of 3 weeks, but the date is coincident. On a normal day 50-150 downtime records are created. On our worst day over 200,000 duplicate records were unintentionally created.
The DBA has discovered that the MSSQL audit log was not configured on this table so we do not have data from MSSQL on how the duplicate records were created. Is there a log in Ignition that will prove how often transaction groups were executed? I need to prove or disprove that Ignition was the root cause of the problem and ensure that we have corrected the root cause of the problem.