Just a heads up, Infor CRM has added several triggers into the system as part of the upgrade process. These triggers are used for their ERP integrations. For most customers who don’t use this integration, these are unnecessary objects that will only result in extraneous data being written to tables that are never used (tables start with ERP). Worse, they can impact your ability to manipulate your database with t-sql statements. I recently ran into an issue trying to run an update on the CONTACT table. The update statement would not run- it hung indefinitely. Turns out it was the triggers preventing the update.
I would strongly recommend identifying if you need these triggers in your system. If not it would not be a bad idea to disable them.
Here is a list of the triggers and the table they are in:
| ACCOUNT_INTEGRATION_INSERT | ACCOUNT |
| ACCOUNT_INTEGRATION_CHANGE | ACCOUNT |
| ACCOUNT_TOMBSTONE | ACCOUNT |
| ACTIVITY_INTEGRATION_INSERT | ACTIVITY |
| ACTIVITY_INTEGRATION_CHANGE | ACTIVITY |
| ACTIVITY_INT_INSTEAD_INS | ACTIVITY |
| ACTIVITYATTENDEE_INT_INSTEAD_INS | ACTIVITYATTENDEE |
| ACTIVITYATTENDEE_INTEGRATION_CHANGE | ACTIVITYATTENDEE |
| ACTIVITYATTENDEE_COUNT | ACTIVITYATTENDEE |
| ADDRESS_INTEGRATION_CHANGE | ADDRESS |
| ADHOCGROUP_INTEGRATION_TOMBSTONE | ADHOCGROUP |
| ADHOCGROUP_INTEGRATION_INSERT | ADHOCGROUP |
| CONTACT_TOMBSTONE | CONTACT |
| CONTACT_INTEGRATION_CHANGE | CONTACT |
| CONTACT_INTEGRATION_INSERT | CONTACT |
| USERACTIVITY_TOMBSTONE | USER_ACTIVITY |
| USERACTIVITY_INTEGRATION_CHANGE | USER_ACTIVITY |
| USERACTIVITY_INT_INSTEAD_INS | USER_ACTIVITY |
Yes, deadlocks would be an issue especially during high volume updates like using Scribe. We have run into those types of deadlocks just trying to clean up bad data in the Account and Contact tables by doing mass updates.