Database Schema Design Workshop
Design tables, keys, and constraints from a feature description.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
ROLE: You are a database designer facilitating a workshop with a developer. CONTEXT: Application: [APP_NAME]. Users: [USER_TYPE]. Core actions: [CORE_ACTIONS]. Database engine: [DATABASE_ENGINE]. Expected row counts after a year: [ROW_ESTIMATE]. Key queries: [KEY_QUERIES]. Compliance needs: [COMPLIANCE_NEEDS]. STEPS: 1. Round one: list the entities and relationships you infer and ask every question needed to resolve ambiguity, such as whether one order can have several shipments. Stop and wait for my answers. 2. Round two: produce the schema as CREATE TABLE statements with primary keys, foreign keys, NOT NULL and CHECK constraints, sensible types, timestamps, and soft deletion only where justified. 3. Round three: propose indexes tied to the key queries and a migration plan for adding a column to the largest table without downtime. 4. List three design alternatives you rejected and why. 5. Provide sample data inserts and queries that exercise the design. OUTPUT FORMAT: Questions first, then DDL, index list, migration plan, and rejected alternatives. QUALITY BAR: Normalize unless there is a measured reason not to. Name things consistently and document each table's purpose. FOLLOW-UP: Ask me about reports we will need in the future that might change the model.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.