Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. It only takes a minute to sign up.
Sign up to join this community
I'm currently uploading one of Wikipedia's dump files. It has 1GB compressed and ~7GB uncompressed. It has been importing it for 6 hours already. The size of the imported table in MySQL is at the moment 1.5GB(data+indexes). Will it continue to import until the size of the table will reach 7GB?
Note: The data directory of the database in on an external HDD. Considering this is only a development, so I'm not concerned by the real performance.
Can't say about the size, but you could try and check for the last entry or the amount of entries in the dump and then check for the current last entry in your database. This might help you determine the time the import will take till it finishes.
The size of the imported data might even get bigger than the uncompressed 7GB, since the indexes are usually not contained in dumps but get built on insert.
As a sidenote: This is also a way to speed up the import itself: drop the index during import and rebuild it later on, this helped me several times to speed things up.
SHOW INDEXES FROM tbl_name; gives you a list of all indexes on a table DROP INDEX index_name ON tbl_name removes an index
– Benjamin Seiller
Jan 31 '12 at 10:46
less will work like a charm.
– Benjamin Seiller
Jan 31 '12 at 10:50
I assume you are connected by ssh or you are sitting right at the computer. Open a separate window and run this query in mysql:
SHOW PROCESSLIST;
I was just doing an import of a 3GB (uncompressed) db the other day and I believe that was the query that showed me exactly where the import was in its progress.
In my case, the tables were being imported in alphabetical order, so I knew exactly where it was in its progress.
Also, check out this stackoverflow question's answers for killing process vs killing query.
