Data access

Downloads

Download the complete database or choose a focused table export. Provider files are checked against the provider’s pinned checksums at build time; files DemoDB generates (complete JSON, YAML, PostgreSQL script, inGitDB archive, and the MySQL script written by DataTug and loaded into a real MySQL) are pinned by a lock and validated against the SQLite fixture; the licence notice below names the ones generated for this dataset.

Every file here, including the PostgreSQL script, JSON, YAML, inGitDB archive and MySQL script that DemoDB generates from the pinned fixture, contains AdventureWorks OLTP data from https://github.com/microsoft/sql-server-samples and is licensed MIT. The header of each generated script carries the licence and the attribution. Keep the licence and attribution notices with any copy. Source and licence →

Complete database

Files ready to use.

SQLite126,820,352 bytes file · 35,367,459 gzip transfer · Complete AdventureWorks OLTP export↓PostgreSQL script110,241,326 bytes file · 18,882,180 gzip transfer · Complete AdventureWorks OLTP export↓JSON218,424,194 bytes file · 19,690,306 gzip transfer · Complete AdventureWorks OLTP export↓YAML243,068,731 bytes file · 19,860,313 gzip transfer · Complete AdventureWorks OLTP export↓inGitDB archive24,093,010 bytes · Complete AdventureWorks OLTP export↓MySQL script102,992,959 bytes file · 18,560,158 gzip transfer · Complete AdventureWorks OLTP export↓SQL (SQLite dialect)139,135,950 bytes file · 19,280,448 gzip transfer · Complete AdventureWorks OLTP export↓

Not offered

Formats without a download.

SQL Server scriptPlanned: Microsoft's AdventureWorks installer needs SQL Server features and 68 BULK INSERT files and is not a single script; the pinned fixture is its SQLite conversion. DemoDB's SQL Server script will be generated by the DataTug SQL-script exporter (dialect mssql, in review and not yet released) from the pinned SQLite fixture, and is published only after it has loaded and verified on a real SQL Server.
Oracle scriptPlanned: The DataTug SQL-script exporter has no Oracle dialect yet, so DemoDB has no generated Oracle script for the pinned SQLite fixture, and no Oracle Database has loaded one. Nothing unverified is published.

Machine-readable schema

Use the contract too.

Schema JSON describes native table and view names, columns, keys, relationships, sample rows, and row counts.

Download schema JSON →

Open the machine-readable DemoDB corpus index →

Reproducible research

One checked snapshot.

The deterministic bundle contains the checked table exports, schema, provider model files, licences, source revision, and example queries. Its manifest lists a SHA-256 checksum for every bundled file and archive part.

Research ZIP part 1 of 520,971,520 bytes · SHA-256 9a5d586d7779ce91fbb141f5daa5f453daf7b0e49387f892fba7f5c24c33ef30↓Research ZIP part 2 of 520,971,520 bytes · SHA-256 eb00b80f73cb1e124441ec4b2515e0f5bb108ac65e53d094646149424490c41b↓Research ZIP part 3 of 520,971,520 bytes · SHA-256 faf45183fc6b45868416010ae5e749f8a6449f2f69b7068c426ab29650cefeb8↓Research ZIP part 4 of 520,971,520 bytes · SHA-256 c351734b030d0f0c1fc86901706e3628ca610d643b3f88e7c10590d0d3ba8cf3↓Research ZIP part 5 of 58,719,856 bytes · SHA-256 3e2c8ed2236454e326a036d18c958f16f0417e9e41a6c3210bceccb8ba14879d↓ Bundle manifestContents, source revision, and file checksums↗ Archive SHA-256Verify the downloaded ZIP↗

Download every part, then concatenate them in numbered order to recreate the ZIP. The manifest lists each part checksum and the complete archive checksum.

Optional browser copy

Explore locally in this browser.

Import every physical table into this browser’s IndexedDB. Nothing is downloaded until you start. Views and the source files stay unchanged; the import is read-only.

The importer verifies the decoded export checksum and declared row count before it activates the new local copy. It uses native primary keys when present; keyless rows are kept in provider JSON export order for local traversal.

No local copy is active.