MySQL also supported ARCHIVE Storage Engine which is basically used for storing large amounts of unindexed DATA.
It does not support any type of Indexes, Foreign keys, Concurrency Control and Transactions.
The performance of ARCHIVE Storage Engine is excellent for storing and supporting billions of data.
For any RDBMS system, Bulk Insertion and other Bulk Operations are common.
To increase the performance of BULK Operation, DBA can disable the indexes, can remove the constraints, can compress the table.
But this all are the default settings of the MySQL ARCHIVE Storage Engine.
When you create an ARCHIVE table, the server creates a table format file in the database directory.
The file begins with the table name and has an .frm extension. The storage engine creates other files, all having names beginning with the table name.
The data file has an extension of .ARZ. And .ARN file may appear during optimization operations.
The ARCHIVE engine also uses zlib lossless data compression, so rows are compressed as they are inserted.
We can use OPTIMIZE TABLE to analyze the table and pack it into a smaller format.
Create a sample table using ARCHIVE Storage Engine:
CREATE TABLE tbl_Students
RNO INT NOT NULL
,StudName VARCHAR(20) NOT NULL
)ENGINE = ARCHIVE ;
Insert few sample records:
INSERT INTO tbl_Students
Check the result:
SELECT *FROM tbl_Students;
| RNO | StudName |
| 1 | Anvesh |
| 2 | Neevan |
| 3 | Jeeny |
| 4 | Roy |
Please share your ideas and opinions about this topic with me, your contribution will add true value to this topic.
If anyone has doubts on this topic then please do let me know by leaving comments or send me an email.
If you like this post, then please share it with others.
Please follow dbrnd.com, I will share my experience towards the success of Database Research and Development Activity.
I put up a post every day, please keep reading and learning.
Discover Yourself, Happy Blogging !
Anvesh M. Patel.