Where this offering fits
Database Performance Analyzer is a database-diagnosis enquiry. The objective should identify the workloads and symptoms the team needs to investigate, such as slow transactions or recurring contention. Database health cannot be inferred from host resource graphs alone.
Architecture and rollout decisions
Confirm supported database engines, versions and collection requirements. Pilot during representative workload periods and review findings with the DBA and application owner. Establish access boundaries for query-related information and the operational impact of collection. Recommendations should be validated through approved changes; a diagnostic observation does not authorise a production database modification.
An evaluation scenario for this offering
Use a non-production database or an approved observation window containing a known slow application transaction. Record the transaction and its timing before examining the diagnostic output. Ask the DBA to explain whether the displayed evidence supports the suspected cause or merely coincides with it. Include a normal busy period as a comparison so high activity is not automatically labelled a fault. If an approved change follows, repeat the same application-level measurement under documented conditions. Keep query evidence access restricted and retain the before-and-after basis, rather than accepting an improvement claim solely from a changed dashboard colour.
Evidence to request for this scope
- Identify databases and performance questions in scope.
- Validate collected evidence against a known workload symptom.
- Record DBA review and post-change measurement.