WorkflowFor DevelopersDatabases & Data Engineering

Database Performance Audit.

When database performance is degrading in production and the cause is not obvious.

ChatGPT Β· Claude Β· GeminiΒ·AdvancedΒ·~1950 tokens
Curated by the AIPP team
Last updated 14 May 2026 Β· v3
database-performance-audit-4.md Β· 1950 words
You are a senior {{role}} brought in to help a developer or tech professional complete a {{use_case}} task.

# Context
- Pack: Developers & Tech Professionals
- Category: Databases & Data Engineering
- Use case: Database Performance Audit
- Source task:
  - Conduct a performance audit for a {{database_type}} database showing signs of: {{describe_symptoms_slow_queries_high_cpu_lock_contention_replicat}}.
  - Step 1: Diagnostics: list the 10 most important queries and database metrics to check first, with the SQL or commands to pull them.
  - Step 2: Diagnosis: interpret the findings and identify the root causes.
  - Step 3: Remediation Plan: prioritised list of fixes : indexing, query rewrites, schema changes, configuration tuning : with estimated impact.

# Goal
Diagnostic queries and commands, an interpretation guide for common findings, and a prioritised remediation plan with impact estimates.

# Constraints
- Treat this as a sequential workflow where each step builds on the previous step.
- Keep every step clearly labeled and easy to run separately if needed.
- Avoid generic filler, vague advice, and unsupported claims.
- Make the output specific, practical, and ready to use.

# Output
Diagnostic queries and commands, an interpretation guide for common findings, and a prioritised remediation plan with impact estimates.

The variables to fill in

PlaceholderWhat to put thereExample
{{role}}RoleDBA
{{use_case}}Your specific valuedatabase performance audit
{{database_type}}Database typePostgreSQL
{{describe_symptoms_slow_queries_high_cpu_lock_contention_replicat}}Describe symptoms slow queries high cpu lock contention replicatslow queries

How to customize this prompt

  1. Replace each {{double-curly}} with your real context.
  2. Adjust the constraints section to match your tone β€” formal, casual, blunt.
  3. If the engagement is recurring, change the duration line to mention milestones rather than days.
  4. Run it in your tool of choice. The output should be ready to paste with at most one small edit.

When to use

When database performance is degrading in production and the cause is not obvious.

PRO TIP

The slow query log is always the starting point β€” enable it if it's not already on, and review the top 10 slowest queries by total time, not just single-run time.

Related prompts

Structured

Technical Problem Debugger

Debug this problem systematically. Identify the root cause, explain why it is happening, provide the fix, and explain how to prevent it in future.

Structured

System Design Advisor

Design the high-level architecture for this system. Cover components, data flow, scaling strategy, and key design decisions.

Structured

No-Code Tool Selector

Recommend the best no-code or low-code tool stack for the stated goal, with implementation guidance.

Structured

Data Analysis Prompt

Design the complete analysis approach for the stated question. Include the analytical method, the steps to execute it, and the format for presenting findings.

β˜… THIS PROMPT IS IN A PACK

The Developer Toolkit Pack

250 technical prompts for code review, documentation, architecture planning, debugging, test writing, API design, and career growth β€” built by developers for developers.

Browse more prompts β†’