From Double-Digit P1s to Near-Zero
Case Study · Sybase Production Support

From Double-Digit P1s to Near-Zero

A healthcare network's Sybase ASE platform had no proactive monitoring and was firefighting P1 incidents monthly. MDA-based alerting and a 3-tier escalation model turned reactive support into a stable operation.

Healthcare Network MDA Monitoring Tempdb Watermarks ASE 16
11 → 1
P1s per month
Industry
Healthcare network
3 Months
Duration to stabilize
The Challenge

An Operation Stuck in Constant Firefighting Mode

Reactive Support

Averaging 11 P1 Incidents a Month

The client's patient records and scheduling platform, running on Sybase ASE, was generating an average of 11 P1-level incidents per month — each one discovered only after clinical staff reported the system was down or unresponsive.

No Monitoring

Zero Proactive Visibility Into the Database

There was no monitoring layer watching tempdb pressure, lock contention, or session activity — the first sign of a problem was always a user-reported outage, never an internal alert.

Unstructured Escalation

Every Incident Went Straight to the Most Senior DBA

With no tiered support structure, every incident — from a routine lock wait to a full instance outage — landed directly on the one senior DBA available, creating both burnout risk and inconsistent response times.

How We Solved It

Catch It Before It's a P1, Route It to the Right Tier

The goal was never to respond to incidents faster — it was to prevent most of them from reaching P1 severity at all.

MDA Baseline & Incident Pattern Review

Reviewed six months of incident history against captured MDA metrics to identify which categories of P1 — tempdb exhaustion, lock contention, replication breaks — were recurring and therefore preventable.

Tempdb Watermark Alerting

Deployed monTempdbActivity-based alerting at 70%, 85%, and 95% tempdb space watermarks, giving the team a warning window before space exhaustion could cascade into an outage.

Session & Lock Contention Monitoring

Added monProcessActivity and monDeadlock-based monitoring tuned to the platform's actual clinical-hours load profile, catching blocking chains before they degraded into a user-visible outage.

3-Tier Escalation Model

Introduced a structured L1/L2/L3 escalation path with documented runbooks for known issue categories, so routine incidents were resolved at L1 and only genuine complexity reached senior engineers.

Weekly Health Reports

Introduced weekly ASE health reports covering tempdb trends, cache hit ratios, and slow-query patterns, turning what had been silent degradation into a visible, trackable trend line.

~90% Fewer P1 Incidents in 3 Months Monthly P1s dropped from an average of 11 to roughly 1 by catching tempdb exhaustion, lock contention, and replication issues before they escalated to outage severity.
Patient-Facing Outages Caught Before Clinical Staff Noticed MDA-based watermark and lock-contention alerting shifted detection from "a clinician reports the system is down" to an internal alert minutes ahead of impact.
Senior DBA Time Reclaimed From Constant Firefighting A 3-tier L1/L2/L3 escalation model resolved routine issues without involving the one senior DBA, freeing that capacity for proactive capacity planning instead of reactive triage.
Stabilized in a Single Quarter The shift from reactive firefighting to a proactive, monitored operation was achieved in three months — not a multi-year support overhaul.
The Impact

The Business Impact

  • P1 incidents reduced from an average of 11 per month to roughly 1 per month within three months
  • Tempdb watermark alerting at 70/85/95% catching pressure before it caused an outage
  • 3-tier L1/L2/L3 escalation model in place with documented runbooks for known issues
  • Weekly ASE health reports giving the client's IT leadership ongoing visibility
  • Senior DBA time redirected from firefighting to proactive capacity planning
  • Clinical staff no longer the first to discover a database problem
"We went from bracing for the next outage every week to genuinely forgetting the database was even there — which, for a system clinicians depend on all day, is exactly what we wanted." — OptiSol Sybase Production Support Lead

Let's Talk

Start a Conversation

Tell us what you are running today and where you need expert support.

"*" indicates required fields

Free initial consultation Confidential assessment solutions@optisolbusiness.com

Global Presence

Where We Operate

Five global locations. One connected engineering team.

New York skyline representing the United States office
HQ

United States

North America

India landmark representing the delivery centre
Delivery Hub

India

Chennai · Coimbatore

London skyline representing the United Kingdom office
Europe

United Kingdom

Client services

Australian coastline representing the Australia office
APAC

Australia

Regional operations

Dubai skyline representing the UAE office
Middle East

UAE

Client services