Sedillo, Derek (Mission Systems) wrote:
Do you think that 2 million records are too many to use with the import
utility?
Import utility can handle so many records. I have tested it with
importing 6 million records into a empty table and it took 18minutes on
my test machine
(RHEL AS 4, Linux 2.6kernel, ibm142, 2cpu 2.8 intel xeon, 4GRam,scsi disks )
Details:
========
Derby ( the current trunk version 10.3), embedded mode.
Input file: :
sh-3.00$ ls -l customer.txt
-rw-r--r-- 1 cloudtst RAND 2362796422 Mar 14 16:10 customer.txt
sh-3.00$ java -version
java version "1.4.2"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2)
Classic VM (build 1.4.2, J2RE 1.4.2 IBM build cxia32142-20061124 (SR7)
(JIT enabled: jitc))
Dataset is from one of the derby system tests (OE) which is based on
TPC-C benchmark.
Data in the customer.txt is the data exported from a customer table
after loading data with scale of 200.
Table schema:.
CREATE TABLE CUSTOMER2 (
C_ID INTEGER NOT NULL,
C_D_ID SMALLINT NOT NULL,
C_W_ID SMALLINT NOT NULL,
C_FIRST VARCHAR(16) NOT NULL,
C_MIDDLE CHAR(2) NOT NULL,
C_LAST VARCHAR(16) NOT NULL,
C_STREET_1 VARCHAR(20) NOT NULL,
C_STREET_2 VARCHAR(20) NOT NULL,
C_CITY VARCHAR(20) NOT NULL,
C_STATE CHAR(2) NOT NULL,
C_ZIP CHAR(9) NOT NULL,
C_PHONE CHAR(16) NOT NULL,
C_SINCE TIMESTAMP NOT NULL,
C_CREDIT CHAR(2) NOT NULL,
C_CREDIT_LIM DECIMAL(12,2) NOT NULL,
C_DISCOUNT DECIMAL(4,4) NOT NULL,
C_BALANCE DECIMAL(12,2) NOT NULL,
C_YTD_PAYMENT DECIMAL(12,2) NOT NULL,
C_PAYMENT_CNT INTEGER NOT NULL,
C_DELIVERY_CNT INTEGER NOT NULL,
C_DATA VARCHAR(500) NOT NULL
);
HTH,
Sunitha.
