MFG Data Archive copies data from manufacturing tables in a LIVE company database into the same tables in an ARCHIVE database.
In a live database many of the SQL tables have triggers on them that perform additional activities when a record is added to, removed from, or updated in, a table. These triggers help maintain data integrity across multiple tables so that, for example, if a Manufacturing Order is deleted from one table it automatically is removed from other tables.
Since the Archive is not used to create transactions, the triggers do not serve a purpose. In fact, they can interfere with the archiving process by attempting to create records in other tables during the archiving process, and the archive utility will populate those other tables with the original records.
MFG Data Archive has a setup utility to Drop All Triggers from the archive database. If this utility is not run, you can receive Violation of Primary Key Constraint errors. This happens because when the archive adds a record to a table, such as PK010033, a trigger automatically adds a record to MOP1400. When the archive attempts to archive MOP1400 it will already contain matching records.
See this section of the MFG Data Archive documentation for more detail on running the Drop All Triggers utility: