My Mekorma Historical Archive tables in SQL have grown exceedingly large and Mekorma check printing performance is compromised. What can I do?

November 15, 2022 Image archive, historical tables 255

In cases we have seen where the Mekorma Check Image Archive has grown to a point where performance is impacted,  we would have to recommend  the client leverage the GP historical inquiry (Recreate Check Stub) for auditing purposes. Note, all payments processed and posted to the GL and registered in the GP Inquiry system with Mekorma Check Image Archive enabled will contain Mekorma check copies, but for auditing purposes we recommend using the GP Inquiry system. 

 

Going forward, if agreeable to utilize the GP inquiry, you may switch off the Mekorma Check Image Archive (Disable at Mekorma System Options). Alternately if you prefer to continue utilizing the Mekorma system for archiving, you would need to back up the current Mekorma archive because it has now grown to an  unmanageable size.

 

Recommendation would be to first back up the tables shown below, and subsequent elimination of the objects  from the HIstorical Audit Tables category in production, then re-running the Mekorma table maintenance routine would be the pathway.

 

Historical Audit Tables

Technical Name

DB

DB Name

Description

ME_CheckAudit_HIST

Company

ME240459

Master record for the batch

ME_CheckAuditHDR_HIST

Company

ME240461

Header record for each check in the batch

ME_CheckAuditGenInfo_HIST

Company

ME240463

Header records for common data for all checks

ME_CheckAuditDetail_HIST

Company

ME240457

Detailed records describing each check

ME_CheckAuditCurrencyDetail_HIST

Company

ME240458

Detailed records describing currency information for the check