Audit request
This is a lightweight request page for teams that need direction before an audit starts. Send a short email with safe context, and the response will point you toward broad database optimization scope, the PostgreSQL specialist path, or triage when the right route is unclear.
Request type
The request should describe what decision you need. It does not need a production login, a data dump, or an upload.
Use this when the symptom may involve queries, indexes, table growth, capacity limits, release timing, or database-adjacent application behavior. The first response helps frame the audit scope and evidence list.
Use this when the system is PostgreSQL and you already expect a specialist review. PostgreSQL-ready teams can continue directly to the collector report path for the current focused workflow.
Use this when the team knows the user-visible symptom but does not know whether the bottleneck is SQL, indexes, table health, hosting capacity, configuration, or application behavior.
What to send
Keep the first email short. Sanitized excerpts and plain-language symptoms are enough for initial routing.
Database engine if known, hosting context, affected workflow, when the slowdown appears, error or timeout pattern, and business impact.
Representative query shapes, sanitized EXPLAIN output, index list excerpts, table size notes, slow log summaries, charts, or checklist answers.
Read-only limits, data sensitivity, maintenance windows, staging availability, approval owners, rollback expectations, and changes that are off limits.
Say whether you need an evidence list, audit scope, PostgreSQL handoff, report expectation, or triage before deciding what to collect next.
Response
The first response is routing and scope guidance, not an automatic performance report.
| Topic | Expectation |
|---|---|
| Deliverable | A short reply that identifies the likely request path, useful evidence to gather next, safety boundaries, and whether a PostgreSQL specialist path is more appropriate. |
| Timing | Expect a human review response, usually within one to two business days after enough context is provided. Complex or unclear cases may need follow-up questions. |
| PostgreSQL-ready teams | If you already know the database is PostgreSQL and can prepare collector-style evidence, use the PostgreSQL collector report path instead of waiting for broad triage. |
| Not promised | This request page does not promise complete support for every database engine, does not produce automatic reports, and does not approve production changes. |
Safety boundary
The request should help define scope without expanding access too early.
Do not send production credentials, unrestricted connection strings, secrets, private keys, or raw customer data in the first request email.
This page is not a SaaS form, account area, hosted collector, or file upload destination. Use email for initial routing only.
A request does not create indexes, rewrite SQL, change configuration, run migrations, vacuum tables, or schedule maintenance automatically.
Any production action needs a human owner, staging test where practical, rollback path, maintenance plan, and explicit approval from your side.
Email support@databaseoptimizationtool.com with the request type, safe evidence, constraints, and desired next step. PostgreSQL-ready users can go straight to the PostgreSQL collector report path.