MySQL Tutorial
MySQL Installation and Configuration
MySQL Database Operations
Database Design
MySQL Data Types
MySQL Storage Engines
MySQL Basic Operations of Tables
MySQL Constraints
MySQL Operators
MySQL Function
MySQL Manipulate Table Data
MySQL View
MySQL Indexes
MySQL Stored Procedure
MySQL Trigger
MySQL Transactions
MySQL Character Set
MySQL User Management
MySQL Database Backup and Recovery
MySQL Log
MySQL Performance Optimization
In MySQL, the data files' representation on the file system depends on the storage engine used. Here's how some common storage engines represent data:
1. InnoDB:
ibdata1
: This is the system tablespace file. By default, it includes the doublewrite buffer, the change buffer, undo logs, and the data dictionary.ib_logfile0
, ib_logfile1
: These are the redo log files..frm
: For each InnoDB table, there is an .frm file in the database directory, which stores the table format..ibd
: If the innodb_file_per_table
configuration option is enabled, each InnoDB table will have its own .ibd file for storing data and indexes.2. MyISAM:
For each MyISAM table, three files are created with the names beginning with the table name and having extensions to indicate the file type:
.frm
file: Storing the table definition..MYD
(MYData): Containing the actual row data..MYI
(MYIndex): Storing the index of the table.3. CSV and ARCHIVE:
.frm
file: Storing the table definition..CSV
for CSV engine: Containing the actual row data..ARZ
for ARCHIVE engine: Containing the actual row data.4. MEMORY/HEAP:
The MEMORY storage engine creates only one file for table definition (.frm). It does not store any data or index on disk.
Remember, these files are typically stored in the MySQL data directory, and the structure may vary based on the version of MySQL and specific configurations. Always refer to the appropriate MySQL documentation for the version you're using to understand the specific details.