Skip to main content
Tony is CloudThinker’s database expert, specializing in query optimization, performance tuning, backup strategies, and data analytics across SQL and NoSQL platforms.

The problem Tony solves

Database performance degrades silently. A missing index on a growing table is invisible until P95 latency spikes and engineers wake up at 2 AM. Connection pool exhaustion looks like an application bug until someone checks the database. Slow queries consume 80% of database CPU while running hundreds of times per day — and nobody knows because there’s no system connecting query analytics to infrastructure cost. Diagnosing and fixing these problems normally requires:
  • Querying pg_stat_statements or enabling MySQL slow query log
  • Reading and interpreting execution plans (EXPLAIN ANALYZE output)
  • Cross-referencing query patterns against current indexes
  • Understanding PostgreSQL/MySQL configuration parameters and their tradeoffs
This is deep specialist work. Most teams don’t have a dedicated DBA, so database performance issues either go unfixed or require expensive consultants.

What other tools miss

Tony goes beyond monitoring: it reads execution plans, understands your schema context, and tells you exactly which index to create, which query to rewrite, and what configuration change to make — in plain language.

How Tony works

  1. Connects to your databases via read access — pg_stat_statements, MySQL Performance Schema, RDS Performance Insights, Aurora, MongoDB profiler
  2. Identifies slow queries by analyzing execution times, call frequency, and resource consumption — finding the highest-impact targets automatically
  3. Reads execution plans — interprets EXPLAIN ANALYZE output to understand table scans, index misses, and join inefficiencies
  4. Recommends with precision — generates specific CREATE INDEX statements, query rewrites, and configuration changes with before/after impact estimates
  5. Understands tradeoffs — considers write overhead of new indexes, memory implications of configuration changes, and downtime requirements for schema changes

Capabilities


Supported platforms


Prompt patterns

Query analysis

Performance optimization

Database health

Backup & recovery


Tool usage

Examples with tools


Effective prompts

Tip: Include metrics
Tip: Specify platform

Connection requirements

Tony requires database connections with performance metrics access:

Common workflows

Performance crisis response

Proactive optimization

Capacity planning


Next steps

PostgreSQL Connection

Connect Tony to your PostgreSQL databases

MySQL Connection

Connect Tony to your MySQL databases

Deep Response Engine

How Tony investigates database-related incidents automatically

Anna

Coordinate Tony with Alex for infrastructure + database cost optimization