sybase production support

02 — Sybase Engineering

Sybase Production Support — Incident Response & 24/7 Monitoring

Named on-call engineers, SLA-backed monitoring, and proactive health checks for Sybase ASE and SAP ASA — escalation paths defined before incidents happen, not during them.

24/7 On-Call Coverage
SLA-Backed Response Guaranteed
Named Engineer Assigned
🛡️ Sybase ASE · SAP ASA
Talk to us → ← Sybase Engineering
What We Cover

Six pillars of Sybase production support

From the moment an alert fires through post-incident review and capacity planning — everything your Sybase ASE and SAP ASA estate needs to stay stable and observable.

24/7 Incident Response

Named on-call engineer with agreed SLA tiers for P1, P2, and P3 incidents. When production breaks, a person picks up — not a ticket queue waiting for Monday morning.

Performance Monitoring

Sybase MDA tables, monProcessActivity, and monDeadlock monitoring with custom alerting thresholds mapped to your OLTP peaks and batch windows — not off-the-shelf defaults that fire false alarms.

Proactive Health Checks

Weekly ASE health reports covering disk space, lock contention, tempdb usage, and slow query identification — catching problems before they escalate into incidents.

Root Cause Analysis

Every P1 and P2 incident gets a written root cause report covering the symptom, the underlying cause, the fix applied, and steps taken to prevent recurrence — not just a ticket closure note.

Backup & Recovery Assurance

Backup job monitoring with alerting on missed or failed runs, weekly restore tests to confirm recovery integrity, and DR run-throughs on an agreed schedule — so you know backups actually work.

Capacity & Growth Reporting

Monthly trend reports on data growth, tempdb pressure, and cache hit ratios — so storage and compute are provisioned ahead of demand, not scrambled for after the fact.

Support Model

Three-tier escalation structure

Every ticket enters at L1 and escalates only as far as needed — keeping Sybase expert time focused on genuine complexity, not routine triage.

L1
First Line Support
Triage & initial response

First point of contact. Ticket intake, priority classification, and resolution of known issues using documented Sybase runbooks.

  • Ticket intake via email, portal, or phone
  • Priority assignment (P1–P4) — SLA clock starts
  • Resolution of known / low-complexity ASE issues
  • Escalation to L2 when runbook threshold is met
L2
Technical Support
Investigation & fix

Senior Sybase engineers who diagnose root causes using MDA tables, develop fixes, and manage change-controlled deployments.

  • Deep-dive MDA / monProcessActivity investigation
  • Lock contention & deadlock analysis via monDeadlock
  • Patch development & staging validation
  • Escalation to L3 for architectural-level failures
L3
Expert Escalation
Architecture & critical resolution

Principal Sybase architects for P1 critical incidents, Replication Server failures, and issues requiring engine-level or architectural changes.

  • P1 critical: production down, instance unreachable
  • Replication Server & Backup Server failure resolution
  • Root cause analysis & written post-incident report
  • Architecture recommendations to prevent recurrence
Service Level Agreement

SLA Matrix

Agreed response and resolution targets by priority — so you always know what to expect when something goes wrong with your Sybase environment.

Priority Criteria / Impact Sybase Examples Response Time Resolution Target Owner
P1 — Critical Production ASE/ASA instance down. Business operations fully halted. Instance crash, login failure, Backup Server down, Replication break ≤ 15 minutes ≤ 4 hours L2 + L3
P2 — High Major functionality impaired. Significant business impact. Severe lock contention, tempdb exhaustion, key stored procedure failures ≤ 1 hour ≤ 8 hours L2
P3 — Medium Partial functionality impacted. Workaround available. Slow query performance, non-critical job failures, cache hit degradation ≤ 4 hours ≤ 2 business days L1 / L2
P4 — Low Minor issue or advisory. No immediate business impact. Capacity advisory, configuration improvement requests, scheduled maintenance ≤ 1 business day ≤ 5 business days L1

* Response times are measured from ticket receipt during agreed support hours. SLAs are customised per engagement. 24×7 coverage available for P1/P2 on all plans.

Incident Lifecycle

From raised to closed & documented

Every Sybase incident follows a structured lifecycle — from the moment it's raised to the moment it's closed with a written root cause on file.

Ticket Raised
Email, portal,
or phone
L1 Triage
Priority assigned,
SLA clock starts
MDA Investigation
monProcessActivity
& MDA queries
Fix & Test
Patch developed
& staging-validated
Deployment
Change-managed
release to prod
Client Sign-off
User confirmation
required to close
RCA & Runbook
Written report &
runbook updated
Monitoring Methodology

MDA-based monitoring, tuned to your workload

Sybase ASE's Management Detail Architecture (MDA) tables give deep, real-time visibility into engine behaviour — we build alerting around them mapped to your actual load profile.

Sessions & Activity
Process & Session Monitoring

Continuous polling of active sessions, wait states, and CPU consumption. Alerts fire when sessions exceed threshold or when a query exceeds agreed runtime limits.

monProcessActivity
Locking
Deadlock & Lock Contention

Deadlock detection and lock wait chain analysis to identify blocking sessions before they cascade. Threshold-based alerting triggers before a user notices degradation.

monDeadlock monLocks
Tempdb
Tempdb Pressure Tracking

Real-time tempdb space utilisation monitoring with alerts at configurable watermarks — 70%, 85%, and 95% — so tempdb exhaustion never reaches a production incident.

monTempdbActivity
Cache & Memory
Cache Hit Ratio & Memory

Data and procedure cache hit ratio tracked over time. Degradation below agreed baselines triggers an investigation before query response times deteriorate.

monDataCache
Backup
Backup Job Assurance

Every backup job monitored for completion and failure. Missed or errored runs trigger immediate alert. Weekly restore tests confirm actual recoverability — not just backup log confirmation.

Sybase Backup Server
Replication
Replication Server Health

Replication Server latency and queue depth monitored continuously. Latency drift above threshold raises a warning; queue backlog triggers immediate L2 investigation.

rs_status admin who,rs
How We Work

Support built around your Sybase environment, not a generic template

SLAs agreed in writing before go-live. Response times, escalation contacts, and out-of-hours cover are confirmed upfront — no "best effort" clauses, no vague paths defined at 2am.

A named engineer who knows your environment. They attend onboarding, review your MDA baselines, and are the person paged when a P1 fires — not whoever is on duty that night.

Alerting tuned to your actual workload. Thresholds reflect your OLTP peaks, batch windows, and month-end cycles — suppressing noise during expected load and amplifying genuine anomalies.

How it works in practice
L1 / L2 / L3 support tiers — structured escalation, each tier with defined ownership
P1 response < 15 minutes — SLA clock starts from first alert receipt
Weekly health reports — space, locks, tempdb, slow queries reviewed every week
Post-incident RCA included — written report for every P1 and P2, no extra charge
Sybase MDA-based monitoring — monProcessActivity, monDeadlock, and custom MDA queries tuned to your workload
Monthly capacity review — growth trends, tempdb pressure, and cache hit ratio reported each month
Our Process

From onboarding to live cover in four steps

A structured engagement so monitoring is tuned and SLAs are confirmed before the first incident — not configured reactively afterwards.

Step 1
Onboarding & Baseline

Connect to your ASE or ASA environment, capture baseline MDA metrics across your typical load profile, and agree SLAs and escalation contacts in writing before going live.

Step 2
Monitoring Setup

Deploy custom MDA-based alerting tuned to your OLTP peaks, batch windows, and month-end cycles — not default thresholds that produce noise and missed alerts in equal measure.

Step 3
Live Support

Named on-call cover begins. Incidents are triaged within SLA, root cause documented during resolution, fix applied and verified in the environment before ticket closure.

Step 4
Continuous Improvement

Monthly review of incident trends, capacity reports, and proactive recommendations — so the environment gets more stable over time, not just stabilised after each event.

Tech & Tools

What we work with

Monitoring and tooling chosen for Sybase — not adapted from an Oracle or SQL Server stack. Every tool below is one our engineers use day-to-day on live Sybase environments.

Sybase ASE 16 SAP ASA / SQL Anywhere Sybase MDA Tables monProcessActivity Sybase Central dBartisan PRTG Nagios PagerDuty Jira Service Management
Case Studies

Sybase Production Support, Real Outcomes

Two recent Sybase production support engagements — from ending a healthcare network's monthly P1 firefighting to putting a written SLA behind a 24/7 dispatch operation.

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