Sales, purchasing, manufacturing, and inventory · adventureworks.demodb.dev
AdventureWorks OLTP
sample database.
Microsoft AdventureWorks OLTP sample database with people, products, sales, purchasing, manufacturing, and inventory.
-- Orders by customer
SELECT h."SalesOrderNumber", c."CustomerID", h."OrderDate", h."TotalDue"
71 tables · 11 views · 759,240 rows
-- 3 high-confidence cross-database table matches
Schema at a glance
Browse the recordsets.
Explore SQLite in DataTug
Known limits.
- Editing needs exactly one primary-key column. 23 of 71 tables here have a composite key or none, so they open read-only: HumanResources.EmployeeDepartmentHistory, HumanResources.EmployeePayHistory, Person.BusinessEntityAddress, Person.BusinessEntityContact, Person.EmailAddress, Person.PersonPhone, Production.ProductCostHistory, Production.ProductDocument, Production.ProductInventory, Production.ProductListPriceHistory, Production.ProductModelIllustration, Production.ProductModelProductDescriptionCulture, Production.ProductProductPhoto, Production.WorkOrderRouting, Purchasing.ProductVendor, Purchasing.PurchaseOrderDetail, Sales.CountryRegionCurrency, Sales.PersonCreditCard, Sales.SalesOrderDetail, Sales.SalesOrderHeaderSalesReason, Sales.SalesPersonQuotaHistory, Sales.SalesTerritoryHistory, Sales.SpecialOfferProduct.
- Views are not listed: the local SQLite browser shows the 71 tables only, not the 11 views. The schema pages on this site list them.
- A table opens with its first 100 rows. There is no paging yet.
Explore PostgreSQL in DataTug
Read-only.
- Explore PostgreSQL in DataTug is read-only by design: you can browse tables and records, but nothing can be edited, deleted or reset.
- It reads the hosted PostgreSQL copy through the public OpenVaultDB server with read-only DTQL queries, never the database directly.
- A table opens with its first 100 rows. There is no paging yet.
- To change data, use the editable local SQLite copy that Explore SQLite in DataTug opens in your browser.
Downloads
Use this fixture
where you work.
Provider files are checked against the provider’s pinned checksums; the complete JSON, YAML, PostgreSQL script, MySQL script and inGitDB archive may be generated from those checked files or by DataTug, and are pinned by a lock; the matrix says which, per dataset. Pick a complete database or a single table.
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 →
Formats not offered for AdventureWorks OLTP
- 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.