Thursday, December 07, 2006

MySQL InnoDB storage engine

MySQL supports a lot of storage engines as well as plugable storage engine architecture. What about referrential integrity of tables with different storage engines ? Foreign keys support avaliable for InnoDB and Falcon. I don't know nothing about Falcon, but InnoDB... It's interesting who is the owner. Answer : Oracle Corporation :) . By the way, if we compare storage engines by this criterias

  1. Storage Limits
  2. Tablespace Support
  3. Configurable Page Sizes
  4. Automatic Storage Extension
  5. ACID Transaction Support
  6. Distributed Transaction Support
  7. Locking Granularity
  8. Savepoint Support
  9. Crash Recovery
  10. Foreign Key Support
  11. B-Tree Indexes
  12. Hash Indexes
  13. Clustered Indexes
  14. Full Text Indexes
  15. Data Caches
  16. Index Caches
  17. Query Cache Support
  18. Online Parameter Support
  19. Geospatial Support
  20. Replication Support
  21. Backup/Point-in-Time Recovery
  22. Memory Footprint
  23. Bulk Insert Speed
we'll see that InnoDB has a most advanced features across competitors. It is the most widely-used. But the insert speed for InnoDB tables is very slow. But nobody forbids to mix up different storage engine types in one database but for different tables to gain owerall performance increase.

No comments: