Re: Efficient way to LOAD large amount of DATA.
Thank you Peter.
Is there any disadvantage -- apart from growing size of the table -- in using MyiSAM instead of InnoDB? these are the MyiSAM features:
Any of these features that could of of concern? i.e. Indexes, Foreign key, etc...
This table primarily be used for SELECT and retrieval. It will not be joint to other tables and there will not be (or very very rarely) be UPDATE, DELETE or INSERTs.
Storage limits 256TB
MVCC No
B-tree indexes Yes
Full-text search indexes Yes
Index caches Yes
Cluster database support No
Backup/point-in-time recovery Yes
Transactions No
Locking granularity Table
Geospatial data type support Yes
Geospatial indexing support Yes
T-tree indexes No
Hash indexes No
Clustered indexes No
Data caches No
Compressed data Yes
Encrypted data Yes
Replication support Yes
Foreign key support No
Query cache support Yes
Update statistics for dd Yes
Subject
Written By
Posted
Re: Efficient way to LOAD large amount of DATA.
May 19, 2016 12:47PM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.