Database Design Simulator | mysimulator.uk

Relational Schema

Normal form 1NF

Rows per table 8

Redundant fields

–

Storage cells

–

Last query time

–

Rows scanned

–

How it works

Each platform is a table: gold cubes are primary keys, teal cubes are foreign keys that reference another table's primary key, green cubes are ordinary attributes and orange cubes are redundant data — a value that is duplicated instead of looked up through a key. Raising the normal form removes transitive and partial dependencies one at a time, turning orange cubes into a single foreign-key reference:

3NF: A -> B -> C  =>  split so A -> B and B -> C
(no attribute depends on a non-key attribute)

Running a query scans the Orders table for one target row. Without an index the engine checks rows one by one — an O(n) linear scan whose cost grows with the row count. With an index on the primary key it jumps straight to the row — close to O(1), so the query time barely changes as the table grows.

Normal form — 1NF keeps duplicated customer/product names inline; 2NF removes one dependency; 3NF removes the rest, leaving only key references.
Rows per table — how many records each table holds; more rows means more to scan without an index.
Index on PK — toggles a primary-key index on the Orders table, changing how the query animation finds its target row.
Run query — searches for one random row and times the search, so you can compare scan cost at different row counts and normal forms.

Primary key Foreign key Attribute Redundant data

⚠ Couldn't load the 3D engineThree.js failed to load from the CDN. Check your connection and reload.