Templates / Booking / Reservation
Reservation System Database Design (ERD Template)
A reservation system database design for venue- or resource-based booking: venues own bookable resources, customers reserve a resource for a time window, payments settle reservations, and each completed reservation can receive exactly one review. RESTRICT rules keep reservation history intact even when cleanup is attempted upstream.
Tables
| Table | Purpose |
|---|---|
customers | People who book |
venues | Physical locations with a timezone |
resources | Bookable units (rooms, courts, seats) |
reservations | Resource ↔ customer with a time window |
payments | Settlements per reservation |
reviews | One review per reservation (UNIQUE FK) |
Schema highlights
- UNIQUE foreign key on reviews.reservation_id — a true 1:1 enforced by the schema
- Reservations RESTRICT against resource/customer deletion to preserve history
- Payments and reviews cascade with their reservation
- Ships with a starter glossary and Email / Money / Status Code domains — naming compliance starts at 100%
How to use it
- Click Open in Sqemo — the template loads as a new local project (nothing is uploaded, no account needed).
- Rename entities and attributes; physical names follow your glossary and naming rules automatically.
-
Export
CREATE TABLESQL for MySQL, PostgreSQL, SQL Server, Oracle, SQLite, H2, or CUBRID — or DBML.
Prefer your own baseline? Import SQL or DBML and Sqemo builds the diagram, foreign keys included.