Document Type | Technical Information
Category | Utility
Document Number | TUTTI016
Overview
This guide compares the sizes according to the table data extraction methods and explains the advantages and disadvantages of each function.
Method
Size Comparison by Each Extraction Method
The extraction query is select * from load_test.
By querying the total size of the LOAD_TEST table using the SQL below, it was confirmed to be approximately 0.87MB.
Method | Size |
|---|---|
Table | 0.87MB |
tbexport | 560k |
export query | 1.1M |
export table | 874k |
load | 2MB |
spool | 3.3MB |
It can be seen that the most efficient method is tbexport, and the least efficient method is spool.
Advantages and Disadvantages of Each Function
Method | Advantages | Disadvantages |
|---|---|---|
tbexport | - Extraction file is compressed, resulting in smaller size - Data filtering for extraction is possible | - Only available in Tibero |
export query | - Extraction file location can be specified - Data filtering for extraction is possible - SAM format allows usage in other databases | - Requires understanding of delimiters |
export table | - Simple to use - SAM format allows usage in other databases | - Data filtering for extraction is not possible |
load | - Simple to use - Extraction file location can be specified - Data filtering for extraction is possible - SAM format allows usage in other databases | - .ctl file is delimited by Position, requiring understanding - SAM file created by Position results in larger size |
spool | - Simple to use - Extraction file location can be specified - Data filtering for extraction is possible | - Requires cleaning of the extracted file |