AdventureWorks ER diagram
Microsoft's flagship OLTP sample — a bicycle manufacturer's people, products, sales, purchasing and HR — rendered from the official install script.
What you're looking at
AdventureWorks is the biggest sample Microsoft ships, and the one that proves a tool can handle real complexity: 46 core tables across five domain schemas (Person, Production, Sales, HumanResources, Purchasing), schema-qualified [Person].[Address] identifiers, multi-column composite keys, and long FK chains from SalesOrderHeader down to CreditCard and CurrencyRate. If a diagram tool survives AdventureWorks, it survives your schema.
46 curated core tables of the 71-table schema — the DDL-audit DatabaseLog table and archive tables are left out. Paste the full install script into the converter for the complete picture.
Nothing above is hand-drawn — the diagram is generated from the official schema file, the same SQL you would paste into the SQL to ER diagram converter.
Working in SQL Server? The SQL Server to ER diagram converter takes any SQL Server DDL — schema dump files, hand-written DDL, or a single CREATE TABLE.
Where the schema comes from
- Source: microsoft/sql-server-samples
- License: MIT (repository license)
- The schema belongs to its original authors; the diagram above was generated by erd.yizuolab.com.
Questions, answered
What is the AdventureWorks database?
AdventureWorks is Microsoft's flagship sample database: the OLTP backend of a fictitious bicycle manufacturer. It is the standard benchmark for SQL Server tooling, and its mix of domain schemas makes it the closest thing to a real production schema among the public samples.
Is this the full schema?
It's the 46 core tables — the five domain areas people actually diagram (Person, Production, Sales, HumanResources, Purchasing). The full install script adds archive tables, DDL auditing (DatabaseLog) and build plumbing. Paste the whole script into the converter if you want the complete map; it parses as-is.
What makes this schema hard for diagram tools?
Schema-qualified identifiers like [Production].[Product], composite primary keys (SalesOrderDetail spans two columns), FK chains five levels deep, and 60+ ALTER TABLE constraint statements separated from their tables by GO batches. Everything above is rendered from that raw script, not a simplified model.
Can I export this diagram?
Yes — SVG and PNG from the toolbar, plus a Mermaid erDiagram text block for your README. The text export carries every table and relationship line, so a schema this size survives into a pull-request description.
Other real schemas
- Chinook ER diagram — SQLite, 11 tables
- Northwind ER diagram — SQL Server, 13 tables
- Pagila ER diagram — PostgreSQL, 16 tables
- All examples · SQL to Mermaid