Oracle schemas generated as Oracle SQL, using Oracle data types and identity columns. Open any of them in the free drawDB editor and export ready-to-run Oracle DDL — tables, keys, indexes and comments.
3 schemas here, from 12 to 13 tables (38 tables and 466 columns in total), written for Oracle. Each one ships an ER diagram you can open and edit, a column-by-column reference, design notes explaining the trade-offs, and SQL for all six dialects. Recurring themes across the set: lending, underwriting.
How a consumer lender models its data in Oracle: applications and verified income, credit decisions with ranked adverse-action reasons, loans, the amortisation schedule as rows, repayments allocated across fees, interest and principal, delinquency buckets and collections.
How a mortgage lender models a file in Oracle: borrowers and co-borrowers with income and liabilities, the subject property and its appraisals, rate locks that expire, underwriting decisions and conditions to clear, a document checklist, closing and disbursement.
School administration in Oracle: students and guardians with custody and contact priority, enrolment history per school year, a period-based timetable with room allocation, attendance per lesson, discipline records, transcripts and a fee ledger.
An experimentation platform end to end: experiments and weighted variants, deterministic hash bucketing, exposure events, metric definitions, per-variant aggregates with sufficient statistics, significance results and staged rollout.
How a short-term rental marketplace models its data: hosts and listings, a host-owned per-night calendar, request-to-book versus instant book, reservations, guest payments and host payouts, and two-way reviews that only reveal once both sides have written.
How a marketplace models many sellers listing the same product: a shared catalogue, competing offers, the buy box decision as a log, orders split into per-seller sub-orders, fulfilment, payouts and product-level reviews.
How a product analytics service stores its data: projects and a discovered event registry, raw events with JSONB properties, anonymous and identified users with identity merges, sessions, funnels, cohorts, retention reports and precomputed metric snapshots.
How an API platform is modelled: consumers and applications, hashed API keys with scopes and rotation, upstream services and routes, rate limit policies, durable usage counters, rolled-up aggregates, sampled request logs, plans, quotas and overage billing.
An ATS modelled end to end: jobs with openings and hiring teams, candidates separate from applications, per-job pipeline stages, interviews with panels, structured scorecards, offers with approval chains and a talent pool of near misses.
How an IT estate is tracked end to end: models versus serialised assets, custody history, software licences and seat allocation with compliance counts, warranties and support contracts, maintenance, depreciation, audits and disposal.
A double-entry bank ledger: accounts in a single currency each, balanced journal entries that are never updated, card authorizations that hold funds, transfers kept separate from postings, and frozen statements.
A content management schema that survives contact with editors: posts with an append-only revision history, categories and tags, threaded comments, a real media library, slug redirects and a double opt-in newsletter list.