ERP SQL performance

The focus here was performance tuning a client-configured ERP application (INFOR) running against SQL Server 2008 and 2012. Symptoms included heavy locking and blocking, plus unusual CPU pressure on the system—symptoms that slowed day-to-day operations without an obvious single “broken” query to blame.

We worked through how the configured ERP actually used the database: where sessions queued, which workloads collided, and what configuration and indexing choices were amplifying CPU and wait time. The goal was a calmer production system, not a rewrite of the ERP itself.

Other duties included moving data to and from the various versions of SQL Server, setting standards and best practices, training staff in DBA tasks, handling installations, and migrating patches into production. That work mattered as much as the tuning: without shared standards, the next patch or data move would recreate the same fire.

When we left, locking and blocking were under control, CPU pressure no longer defined the workday, and the client’s team had clearer practices for installs, data movement, and production patches—so they could keep the ERP healthy without waiting for outside help every time something changed.