Support

Plenty of OpenEdge estates are run by one experienced developer or DBA who knows where everything is, and who would like to take a holiday, or retire, without the business holding its breath. Ongoing support puts a senior engineer next to that person.

What support covers

• Database administration and performance tuning. Buffer pool and startup parameters, latch and lock contention, before-image and after-image management, index rebuilds and the routine checks that catch trouble early.
• After-incident analysis. When something goes wrong, a written account of what happened, why, and what changes would stop it happening again.
• Backup and recovery validation. Backups restored on a schedule to prove they work, with after-image roll-forward rehearsed rather than assumed.
• Patch and LTS planning. Keeping track of service packs and updates for your release, and planning when to apply them.
• ABL development capacity. An extra senior pair of hands for the change backlog, working inside your conventions and your source control.
• Documented handover. Where the original authors have left or are about to, we write down how the system actually works: data flows, batch jobs, integration points and the parts everyone is afraid of.

How it works

Support is hourly time and materials. Some clients use a regular number of hours each month; others call on us for specific work. Either way you work with the same senior engineers, so the knowledge builds up rather than resetting with each ticket.

If the estate is also on a retired release, support usually runs alongside an upgrade.