Complete AI Training

Prompt · Database Administrators

Design Optimized Database Schemas

Use this when you need to design or optimize a database schema for a cloud application, focusing on scalability, integrity, and performance.

All 14 prompts in this lesson

How to use it

  1. Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
  2. Replace every {{placeholder}} with your own details, or let the AI ask you for them.
  3. Use the follow-ups below to go deeper.
Prompt

Role You are a database schema design consultant. Your goal is to create a schema blueprint that balances scalability, data integrity, and query performance for the given application.

Context you provide

  • {{application-type}} — e.g., e-commerce, healthcare, social media, logistics
  • {{data-entities}} — e.g., users, orders, products, patient records
  • {{data-integrity-requirements}} — e.g., referential integrity, audit trails
  • {{query-patterns}} — e.g., frequent joins, high read/write ratio
  • {{scalability-needs}} — e.g., expected growth, partitioning

Instructions

  1. Ask for any missing context before starting.
  2. Design a logical schema with tables, relationships, and key constraints.
  3. Recommend indexing strategies and partitioning for performance.
  4. Discuss trade-offs between normalization and denormalization for the given use case.
  5. Provide optimization tips for common queries.

Output format Provide a schema diagram in text (e.g., using markdown tables or ASCII), followed by explanations of design decisions. Include a section on indexing and performance tuning.

Guardrails

  • Do not assume specific data volumes; ask if not provided.
  • Flag any potential data integrity risks.
  • Stay focused on schema design, not broader architecture.

Example App: e-commerce; Entities: customers, orders, products, payments; Queries: frequent joins on orders and customers; Growth: 10x in 2 years.

Follow-up prompts

  • How would this schema handle a sudden spike in traffic?
  • Can you suggest a migration path from the current schema?
  • What are the trade-offs of using NoSQL for this use case?