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

A collection per table. Each primary key is the document _id; foreign keys are fields under their own names, so the SQL version's joins become $lookup stages.

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
  booth_assignments — 3,000 documents
  booths — 400 documents
  categories — 12 documents
  checkins — 600,000 documents
  coupons — 40 documents
  equipment — 60 documents
  event_categories — 3,000 documents
  event_sponsors — 4,000 documents
  event_vendors — 4,000 documents
  events — 2,000 documents
  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
  session_equipment — 6,000 documents
  session_speakers — 8,000 documents
  sessions — 6,000 documents
  speakers — 200 documents
  sponsors — 40 documents
  sponsorship_packages — 4,000 documents
  staff_assignments — 5,000 documents
  tasks — 8,000 documents
  tickets — 4,000 documents
  user_roles — 10,000 documents
  users — 80,000 documents
  vendors — 50 documents
  venues — 25 documents

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.
