(see Section 16.11, “Overview of MySQL Storage Engine Architecture”).įor information about features offered in commercial MySQL ServerĮditions, on the MySQL website. For advanced users, it alsoĬontains a description of the pluggable storage engine architecture This chapter covers use cases for special-purpose MySQL storageĬhapter 15, The InnoDB Storage Engine andĬhapter 23, MySQL NDB Cluster 8.0. The Support column indicates whether an engineĪn engine is available, not available, or available and currently To determine which storage engines your server supports, use the MySQL Server uses a pluggable storage engine architecture thatĮnables storage engines to be loaded into and unloaded from a Recommends using it for tables except for specialized use cases. The default and most general-purpose storage engine, and Oracle Storage engines are MySQL components that handle the SQL operations The logical design of the database should be centered around data analysis and user requirements the choice to use a relational database would come later, and even later would the choice of MySQL as a relational database management system, and then the selection of a storage engine for each table.Table of Contents 16.1 Setting the Storage Engine 16.2 The MyISAM Storage Engine 16.2.1 MyISAM Startup Options 16.2.2 Space Needed for Keys 16.2.3 MyISAM Table Storage Formats 16.2.4 MyISAM Table Problems 16.3 The MEMORY Storage Engine 16.4 The CSV Storage Engine 16.4.1 Repairing and Checking CSV Tables 16.4.2 CSV Limitations 16.5 The ARCHIVE Storage Engine 16.6 The BLACKHOLE Storage Engine 16.7 The MERGE Storage Engine 16.7.1 MERGE Table Advantages and Disadvantages 16.7.2 MERGE Table Problems 16.8 The FEDERATED Storage Engine 16.8.1 FEDERATED Storage Engine Overview 16.8.2 How to Create FEDERATED Tables 16.8.3 FEDERATED Storage Engine Notes and Tips 16.8.4 FEDERATED Storage Engine Resources 16.9 The EXAMPLE Storage Engine 16.10 Other Storage Engines 16.11 Overview of MySQL Storage Engine Architecture 16.11.1 Pluggable Storage Engine Architecture 16.11.2 The Common Database Server Layer how the application will use the database, how many tables, size of the tables, the transaction load, volumes of select, insert, updates, concurrency requirements, replication features, etc. If not, then MyISAM is up for consideration.Ī more detailed discussion of differences is rather impractical (in this forum) absent a more detailed discussion of the problem space. In choosing between InnoDB and MyISAM, the first step is to determine if we need the features provided by InnoDB. MySQL also has other storage engines, with their own design goals. Those two specific engines you asked about (InnoDB and MyISAM) have different design goals. With MyISAM, a DML statement will obtain an exclusive lock on the table, and while that lock is held, no other session can perform a SELECT or a DML operation on the table. These features are not supported by the MyISAM engine. changes made by two or more DML operations handled as single unit of work, with all of the changes either applied, or all the changes reverted). We choose InnoDB if we need the database to enforce foreign key constraints or support transactions (i.e. The main differences between InnoDB and MyISAM ("with respect to designing a table or database" you asked about) are support for "referential integrity" and "transactions".
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |