Read-only Back to SQLite3 Guide
Northwind Traders

Microsoft's classic sample database, converted to SQLite. Northwind is a small company that imports speciality foods and resells them. It has customers, orders, products, suppliers, staff and sales territories, all joined by keys. Click any table to browse it, follow a key to the row it points at, or write your own query in the SQL console.

This is a demonstration, and nothing here can be changed. You can browse and query freely; any statement that would write is refused. To practise INSERT, UPDATE and DELETE, download northwind.db and open it with sqlite3 northwind.db. The Northwind tab of the SQLite3 guide walks through everything the database was built to teach.
13
Tables
16
Views
3308
Rows in all tables
1996–98
Order dates
How the tables connect
Click a table to open it
Northwind entity-relationship diagram: 13 tables and the foreign keys between them Customers 91 CustomerID PK CompanyName Country CustomerCustomerDemo 0 CustomerID PK FK CustomerTypeID PK FK CustomerDemographics 0 CustomerTypeID PK CustomerDesc Orders 830 OrderID PK CustomerID FK EmployeeID FK ShipVia FK OrderDate Shippers 3 ShipperID PK CompanyName Employees 9 EmployeeID PK LastName ReportsTo FK Order Details 2,155 OrderID PK FK ProductID PK FK UnitPrice Quantity Discount EmployeeTerritories 49 EmployeeID PK FK TerritoryID PK FK Territories 53 TerritoryID PK RegionID FK Products 77 ProductID PK SupplierID FK CategoryID FK UnitPrice Categories 8 CategoryID PK CategoryName Picture Suppliers 29 SupplierID PK CompanyName Region 4 RegionID PK RegionDescription

Each arrow runs from a foreign key (FK) to the primary key (PK) it references: from the “many” side to the “one” side. The number in each header is the table's row count.

Tables
13 tables
Categories8 rows

Eight product groups, each with a bitmap picture stored as a BLOB.
Customers91 rows

Companies that buy from Northwind. A five-letter text key (ALFKI) instead of a number.
Employees9 rows

Nine staff. ReportsTo points back into the same table, which makes the org chart.
Shippers3 rows

Three freight companies. Orders.ShipVia points here.
Suppliers29 rows

Companies Northwind buys from. Each product has exactly one supplier.
Orders830 rows

One row per order: who bought, which employee sold it, which shipper carried it.
Products77 rows

The catalogue: price, stock on hand, stock on order and the reorder level.
Order Details2155 rows

The order lines. Its primary key is two columns, (OrderID, ProductID).
Region4 rows

Four regions: Eastern, Western, Northern, Southern.
Territories53 rows

US sales territories, each in one region.
EmployeeTerritories49 rows

A junction table: which employee covers which sales territory (many-to-many).
CustomerDemographics0 rows

Customer types. Empty in Microsoft's data, kept to show the design.
CustomerCustomerDemo0 rows

Junction table between customers and demographics. Also empty.
Microsoft's views
Saved queries, translated from T-SQL
How this demo stays read-only

The SQL console runs whatever you type, so it is protected in four separate ways. Any one of them would be enough on its own.

  1. The file is opened with mode=ro&immutable=1. SQLite opens it read-only and never takes a lock on it.
  2. PRAGMA query_only = ON makes SQLite refuse any statement that would write.
  3. An authorizer callback checks every statement as it is compiled. It allows only reads, function calls and a few introspection pragmas such as PRAGMA table_info, and it refuses ATTACH, so a query can't open any other file on the server.
  4. The operating system: the web server's user account has no write permission on the file.

Each query is also stopped after 2 seconds and returns at most 500 rows, so one visitor can't tie up the server.