InnoDB storage engine

E97106

MySQL storage engine transactional storage engine

InnoDB storage engine is a widely used transactional storage engine for MySQL that provides ACID compliance, row-level locking, and crash recovery for reliable, high-performance database operations.

Try in SPARQL Jump to: Surface forms Disambiguation Statements Elicitation Referenced by

All labels observed (3)

Label	Occurrences
InnoDB storage engine canonical	3
InnoDB	2
XtraDB	1

How this entity was disambiguated

This entity first appeared as the object of triple T816900 — resolving that mention is where its identity was fixed. The disambiguator weighed these candidate entities and picked the highlighted one (or “None”, minting a new entity). This is how homonymy is resolved: the same surface form can point to different entities.

NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07

Target entity: InnoDB storage engine
Context triple: [MySQL, supportsFeature, InnoDB storage engine]

A. MariaDB
MariaDB is an open-source relational database management system, forked from MySQL, known for its compatibility, performance, and community-driven development.
B. MySQL
MySQL is a widely used open-source relational database management system known for its reliability, performance, and role in powering many web applications and services.
C. PostgreSQL
PostgreSQL is a powerful open-source relational database management system known for its robustness, extensibility, and strong standards compliance.
D. INGRES relational database system
INGRES relational database system is an influential early relational DBMS developed at the University of California, Berkeley, that pioneered many concepts and technologies later adopted by commercial database systems.
E. IBM DB2
IBM DB2 is a family of enterprise-grade relational database management systems developed by IBM, widely used for high-performance, scalable data storage and transaction processing across mainframe, distributed, and cloud environments.
F. None of above. chosen
G. Unsure - the case is ambiguous/there is not enough information to decide.

NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07

Target entity: InnoDB storage engine
Target entity description: InnoDB storage engine is a widely used transactional storage engine for MySQL that provides ACID compliance, row-level locking, and crash recovery for reliable, high-performance database operations.

A. MariaDB
MariaDB is an open-source relational database management system, forked from MySQL, known for its compatibility, performance, and community-driven development.
B. MySQL
MySQL is a widely used open-source relational database management system known for its reliability, performance, and role in powering many web applications and services.
C. PostgreSQL
PostgreSQL is a powerful open-source relational database management system known for its robustness, extensibility, and strong standards compliance.
D. INGRES relational database system
INGRES relational database system is an influential early relational DBMS developed at the University of California, Berkeley, that pioneered many concepts and technologies later adopted by commercial database systems.
E. IBM DB2
IBM DB2 is a family of enterprise-grade relational database management systems developed by IBM, widely used for high-performance, scalable data storage and transaction processing across mainframe, distributed, and cloud environments.
F. None of above. chosen

Statements (51)

Predicate	Object
instanceOf	MySQL storage engine ⓘ transactional storage engine ⓘ
defaultStorageEngineOf	MySQL ⓘ surface form: MySQL 5.5 and later
designedFor	OLTP workloads ⓘ high-concurrency workloads ⓘ
developedFor	MySQL ⓘ surface form: MySQL relational database management system
originallyDevelopedBy	Innobase Oy ⓘ
ownedBy	Oracle Corporation ⓘ
provides	ACID compliance ⓘ automatic recovery after crashes ⓘ crash-safe operations ⓘ data integrity ⓘ referential integrity enforcement ⓘ
storesDataIn	tablespaces ⓘ
supports	ACID transactions ⓘ MVCC ⓘ atomicity ⓘ automatic crash recovery ⓘ buffer pool caching ⓘ clustered indexes ⓘ consistency ⓘ crash recovery ⓘ durability ⓘ foreign key cascading actions ⓘ foreign key constraints ⓘ full-text indexes ⓘ gap locks ⓘ isolation ⓘ locking reads ⓘ multi-version concurrency control ⓘ next-key locks ⓘ non-locking consistent reads ⓘ read committed isolation level ⓘ read uncommitted isolation level ⓘ redo logs ⓘ referential integrity ⓘ repeatable read isolation level ⓘ row-based data storage ⓘ row-level locking ⓘ row-level locking for writes ⓘ savepoints ⓘ secondary indexes ⓘ serializable isolation level ⓘ spatial indexes ⓘ transactions ⓘ undo logs ⓘ
usedFor	reliable, high-performance database operations ⓘ
uses	buffer pool for caching data and indexes ⓘ redo log for crash recovery ⓘ undo log for MVCC ⓘ
writtenIn	C ⓘ

How these facts were elicited

Referenced by (6)

Full triples — surface form annotated when it differs from this entity's canonical label.

MySQL → supportsFeature → InnoDB storage engine ⓘ

MariaDB → supportsStorageEngine → InnoDB storage engine ⓘ

this entity surface form: InnoDB

MariaDB → supportsStorageEngine → InnoDB storage engine ⓘ

this entity surface form: XtraDB

MyISAM storage engine → replacedBy → InnoDB storage engine ⓘ

MyISAM storage engine → recommendedAlternative → InnoDB storage engine ⓘ

TokuDB → comparedWith → InnoDB storage engine ⓘ