Event management sample database — MongoDB, embedded (2,964,981 rows)

Tables that belong to another are folded into it as arrays, so the documents read the way the application uses them. The rest are collections of their own, joined by key as in the flat version.

Load it:
  sh import.sh                    (into mongodb://localhost:27017)
  sh import.sh "<connection string>"

Or one collection at a time: mongoimport --db event-management --collection <name> --file <name>.ndjson

Collections:
  applied_coupons — 100,000 documents
  booths — 400 documents, each with its booth_assignments
  categories — 12 documents
  checkins — 600,000 documents
  coupons — 40 documents
  equipment — 60 documents
  event_sponsors — 4,000 documents
  events — 2,000 documents, each with its event_categories, its event_vendors
  exhibitors — 3,000 documents
  feedbacks — 40,000 documents
  media — 4,000 documents
  notifications — 30,000 documents
  payments — 1,000,000 documents
  profiles — 40,000 documents
  registrations — 1,000,000 documents
  roles — 4 documents
  rooms — 150 documents
  sessions — 6,000 documents, each with its session_equipment, its session_speakers
  speakers — 200 documents
  sponsors — 40 documents
  sponsorship_packages — 4,000 documents
  staff_assignments — 5,000 documents
  tasks — 8,000 documents
  tickets — 4,000 documents
  users — 80,000 documents, each with its user_roles
  vendors — 50 documents
  venues — 25 documents

Folded in (no collection of their own):
  booth_assignments — 3,000 rows, as the "booth_assignments" array on booths (its booth_id is the parent's _id)
  event_categories — 3,000 rows, as the "event_categories" array on events (its event_id is the parent's _id)
  event_vendors — 4,000 rows, as the "event_vendors" array on events (its event_id is the parent's _id)
  session_equipment — 6,000 rows, as the "session_equipment" array on sessions (its session_id is the parent's _id)
  session_speakers — 8,000 rows, as the "session_speakers" array on sessions (its session_id is the parent's _id)
  user_roles — 10,000 rows, as the "user_roles" array on users (its user_id is the parent's _id)

Types: numeric columns are Decimal128, so totals stay exact; dates and timestamps are
Date values read as UTC (the data has no time zone); times and UUIDs are strings;
JSON columns are embedded objects.

Synthetic data, CC0-1.0, from databasesample.com. The same rows as the SQL and CSV files.
