Insurance sample database — MongoDB, embedded (255,185 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 insurance --collection <name> --file <name>.ndjson

Collections:
  addresses — 6,500 documents
  adjusters — 60 documents
  agencies — 12 documents
  agents — 300 documents
  beneficiaries — 2,000 documents
  branches — 40 documents
  claims — 2,000 documents, each with its claim_assessments, its claim_documents, its claim_payments
  commissions — 8,000 documents
  companies — 6 documents
  customers — 6,000 documents, each with its customer_support_tickets
  documents — 4,000 documents
  invoices — 100,000 documents
  medical_providers — 80 documents
  medical_treatments — 400 documents
  payments — 92,000 documents
  policies — 8,000 documents, each with its policy_riders
  policy_categories — 5 documents
  policy_plans — 25 documents
  properties — 2,000 documents
  reinsurance_claims — 200 documents
  reinsurance_companies — 5 documents
  reinsurance_contracts — 12 documents
  renewals — 3,000 documents
  underwriters — 40 documents
  underwriting_assessments — 8,000 documents
  vehicles — 3,000 documents

Folded in (no collection of their own):
  claim_assessments — 2,000 rows, as the "claim_assessments" array on claims (its claim_id is the parent's _id)
  claim_documents — 3,000 rows, as the "claim_documents" array on claims (its claim_id is the parent's _id)
  claim_payments — 1,000 rows, as the "claim_payments" array on claims (its claim_id is the parent's _id)
  customer_support_tickets — 500 rows, as the "customer_support_tickets" array on customers (its customer_id is the parent's _id)
  policy_riders — 3,000 rows, as the "policy_riders" array on policies (its policy_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.
