Deciding to leave Pentaho does not make the nightly load optional. Most organizations need someone who can still fix Kettle problems at 3am for the eighteen to thirty-six months a migration realistically takes.
The nightly load had become unreliable: transformations failing on memory pressure when input volumes grew, jobs that reported success while a partially failed step left the target table half-loaded, and JDBC driver behavior that had changed after a database upgrade. Failures surfaced as business complaints the next morning rather than as alerts overnight.
Pentaho Data Integration on-premises Linux servers, SQL Server and PostgreSQL sources and targets, nightly batch window feeding operational reporting.
AceMQ provides named senior engineers with a 15-minute emergency response SLA and 24/7 coverage — no tier-1 triage queue between the customer and someone who can actually read the transformation. We addressed the recurring failures at the source rather than restarting jobs, and rebuilt the error handling so partial loads fail cleanly.
The recurring nightly failures stopped, and half-loaded target tables were eliminated by making partial failures abort the load. The estate is stable enough that the migration can proceed on plan rather than under emergency pressure.
Resolving Carte slave server instability where long-running clustered transformations hung, leaked memory, and left orphaned carte sessions.
Planning and executing a staged move off Pentaho Data Integration onto a modern ELT stack, without a big-bang cutover of hundreds of transformations.
Whether you need architecture advisory, 24/7 support, or full managed services, AceMQ has the expertise to help.