Page 2 of 2
Re: Large External File Usage
Posted: Tue Feb 07, 2017 12:01 am
by Mikey
By the way, did you already have the indexes set on the table before you started the import?
Re: Large External File Usage
Posted: Tue Feb 07, 2017 10:50 am
by AxWald
Well,
this cannot be this complicated? Have you tried it the simple way?
- Analyze the data, and determine the data types.
I see a VARCHAR, a DATETIME, and 12 FLOATs or DOUBLEs.
- Create a suitable table. Don't forget an additional ID as col 1:
SQLite: INTEGER PRIMARY KEY AUTOINCREMENT NOT NULL,
MySQL: INT(10) NOT NULL AUTO_INCREMENT, set as PRIMARY KEY.
- Split a reasonable part of your data for a test.
- Fire up your db manager, give it the proper information, and try an import.
- Read the error message, correct what you've done wrong.
- Once it has imported your test data, empty the table, VACUUM, and give it the full .csv.
If this doesn't work, tell us what exactly went wrong. Then we can see further ;-)
Have fun!
(PS: if you have access to MS Access, this should work too!)
Re: Large External File Usage
Posted: Thu Feb 09, 2017 1:11 pm
by MaxV
Not a lot of thought wrote:I have a large file 10,000,000+ records roughly 3.5 Gigs. It is in CSV format....
I suggest you to use a:
Code: Select all
BEGIN TRANSACTION;
all you MySQL comamnds;
...
COMMIT;
It would solve your problem.
However a
repeat for each line tLine in CSV would resolve too.