Evidence in one place
Bring relevant execution plans, expensive statements, and runtime metrics into a single diagnostic review.
Analyze execution plans, expensive statements, and runtime metrics. Review likely causes and proposed remediation—with your DBA in control.
Recommendations only. No automatic production changes.

Incident overview
Query-duration review
Synthetic case DEMO-001
Statement reference
STMT-DEMO-01
Illustrative statement · no live connection
Execution-plan comparison
Baseline plan ↔ Affected plan
Compare plan structure, operator runtimes, and row estimates.
Working hypothesis
A plan change may be contributing to increased query duration.
Recommended validation
Compare the affected and baseline plans, operator runtimes, and row estimates before selecting a remediation.
Supporting evidence
Execution plans · baseline and affected
Expensive statement logs · relevant sample
Runtime metrics · operator and row estimates
Proposed SQL
Placeholder-- Proposed SQL appears here after diagnostic review.
Review status
Awaiting DBA review.DB Performance Copilot for SAP HANA brings a structured review to your database-performance cases.
Bring relevant execution plans, expensive statements, and runtime metrics into a single diagnostic review.
Connect suspected bottlenecks to supporting evidence and identify what still needs verification.
Present recommended checks and proposed remediation for senior DBA review.
Collect diagnostics → Analyze evidence → Review recommendations → DBA decides.
Bring together execution plans, expensive statement logs, and runtime metrics.
Compare the available evidence and surface likely causes that need verification.
A senior DBA reviews the supporting evidence, proposed checks, and remediation.
Production execution happens separately, using existing database tools and your change-control process.
Review the evidence, challenge the diagnosis, and approve the next action. The copilot does not execute remediation against production databases.
Inspect the diagnostics behind each working hypothesis.
Validate the likely cause and decide which checks are needed.
Your DBA independently executes approved changes through existing database tools.
Pilot scoping covers hosting region, network boundaries, access controls, data handling, retention, and audit requirements.
An option to assess during scoping, including region, operating responsibilities, and data handling.
An option to assess against your network boundaries, access model, and infrastructure requirements.
Assess deployment fit, retention, access controls, and audit needs before agreeing the pilot scope.
A focused, paid 14–30-day pilot to assess diagnostic usefulness, DBA review effort, and deployment fit before a broader rollout.