MySQL Storage Engines Feature Summary

1
MySQL Storage Engines Feature Summary Feature MyISAM Memory InnoDB Archive NDB Storage limits 256TB RAM 64TB None 384EB Transactions No No Yes No Yes Locking granularity Table Table Row Table Row MVCC No No Yes No No Geospatial data type support Yes No Yes Yes Yes Geospatial indexing support Yes No No No No B-tree indexes Yes Yes Yes No Yes Hash indexes No Yes No[a] No Yes Full-text search indexes Yes No Yes[b] No No Clustered indexes No No Yes No No Data caches No N/A Yes No Yes Index caches Yes N/A Yes No Yes Compressed data Yes[c] No Yes[d] Yes No Encrypted data[e] Yes Yes Yes Yes Yes Cluster database support No No No No Yes Replication support[f] Yes Yes Yes Yes Yes Foreign key support No No Yes No No Backup / point-in-time recovery[g] Yes Yes Yes Yes Yes Query cache support Yes Yes Yes Yes Yes Update statistics for data dictionary Yes Yes Yes Yes Yes [a] InnoDB utilizes hash indexes internally for its Adaptive Hash Index feature. [e] Implemented in the server (via encryption functions), rather than in the storage engine. [b] InnoDB support for FULLTEXT indexes is available in MySQL 5.6.4 and higher. [f] Implemented in the server, rather than in the storage engine. [c] Compressed MyISAM tables are supported only when using the compressed row format. Tables using the compressed row format with MyISAM are read only. [g] Implemented in the server, rather than in the storage engine. [d] Compressed InnoDB tables require the InnoDB Barracuda file format. [e] Implemented in the server (via encryption functions), rather than in the storage engine.

description

Full Name as 1st Name, 2nd Name (if any) and last Name :Gender :Marital StatusDate of Birth: (Mandatory)Current CTC:Expected CTC:Notice Period :Alternate Mail ID:Total IT Experience:Total Relevant Experience (WCF & MVC) :Current Company:Contact Number :Email Id:PAN CARD Number (Mandatory) :Have u applied with ACCENTURE earlier (within last 3 months):Current Location:Able for Walk In on - 4th JAN (SAT).(Y/N)-

Transcript of MySQL Storage Engines Feature Summary

Page 1: MySQL Storage Engines Feature Summary

MySQL Storage Engines Feature Summary

Feature MyISAM Memory InnoDB Archive NDB

Storage limits 256TB RAM 64TB None 384EB

Transactions No No Yes No Yes

Locking granularity Table Table Row Table Row

MVCC No No Yes No No

Geospatial data type support Yes No Yes Yes Yes

Geospatial indexing support Yes No No No No

B-tree indexes Yes Yes Yes No Yes

Hash indexes No Yes No[a] No Yes

Full-text search indexes Yes No Yes[b] No No

Clustered indexes No No Yes No No

Data caches No N/A Yes No Yes

Index caches Yes N/A Yes No Yes

Compressed data Yes[c] No Yes[d] Yes No

Encrypted data[e] Yes Yes Yes Yes Yes

Cluster database support No No No No Yes

Replication support[f] Yes Yes Yes Yes Yes

Foreign key support No No Yes No No

Backup / point-in-time recovery[g] Yes Yes Yes Yes Yes

Query cache support Yes Yes Yes Yes Yes

Update statistics for data dictionary Yes Yes Yes Yes Yes

[a] InnoDB utilizes hash indexes internally for its Adaptive Hash Index feature.

[e] Implemented in the server (via encryption functions), rather than in the storage engine.

[b] InnoDB support for FULLTEXT indexes is available in MySQL 5.6.4 and higher.

[f] Implemented in the server, rather than in the storage engine.

[c] Compressed MyISAM tables are supported only when using the compressed row format. Tables using the compressed row format with MyISAM are read only.

[g] Implemented in the server, rather than in the storage engine.

[d] Compressed InnoDB tables require the InnoDB Barracuda file format.

[e] Implemented in the server (via encryption functions), rather than in the storage engine.