About a year ago I released the Magento CE 184.108.40.206 database diagram and since then, also with the increasing popularity of Magento 2, there have been requests for a Magento 2 database diagram.
This is the database diagram of a fresh CE 2.1.3 installation.
Some statistics (because I love numbers):
- Magento CE 2.1.3 consists of 315 tables (that’s 18 tables less compared to Magento CE 220.127.116.11)
- 1 table starts with core_* (compared to 19 tables in M1)
- 38 tables start with sales_* (compared to 47 tables in M1)
- 76 tables start with catalog_* (compared to 84 tables in M1)
These are the changes I found so far:
- core_resource can was renamed to setup_module
- the core_* prefix was removed: core_layout_link is now layout_link, core_layout_update is now layout_update
- sales_flat_*/sales_* was removed as prefix. For example sales_flat_order is now sales_order.
- setup_module (former core_resource)
- authorization_role (former admin_role)
- authorization_rule (former admin_rule)
- password_reset_request_event (part of the Security module)
- reporting_* tables (for NewRelic Reporting)
- sequence_order_0 (SalesSequence module manages sequences for next system entities and flows for order, invoice, shipment and credit memos)
Removed (=tables you won’t find in the M2 database diagram any more):
- All api_* tables
- All tag_* tables (no more Mage_Tag!)
Here’s the DB diagram of a fresh Magento Community Edition 2.1.3.
I tried to keep at least the bigger parts of the DB diagram similar to the version of the CE 18.104.22.168 db diagram to make it easier to understand what has changed.
The big yellow part on the left are the catalog tables, the big blue part on the right are the sales tables. Inbetween them there are the EAV tables and core tables. The smaller modules are on the bottom part of the db diagram.
If you like it, go an upvote my answer(s) on Magento Stackexchange: