# Unable to restore a mysql database from dump produced by mysqldump **URL:** \ **Category:** Other MySQL® Questions\ **Created:** [March 5, 2010, 8:05am UTC](https://forums.percona.com/t/unable-to-restore-a-mysql-database-from-dump-produced-by-mysqldump/1361 "2010-03-05T08:05:58Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![novice.program](https://avatars.discourse-cdn.com/v4/letter/n/a4c791/32.png) [@novice.program](https://forums.percona.com/u/novice.program)\ **Post date:** [March 5, 2010, 8:05am UTC](https://forums.percona.com/t/unable-to-restore-a-mysql-database-from-dump-produced-by-mysqldump/1361/1 "2010-03-05T08:05:58Z")
Hello All, I have made a dump of my database in which one table is pretty huge (about 4 million records) and has good number of indices(One full text index along with a primary key and 3 unique indices). When i try to restore this dump the restore hangs(its been running for five days now) when it tries to execute the statement which enables keys (ALTER table x ENABLE keys). Any suggestions on how to go about restoring this dump are more than welcome. The table in question is a myisam table. Thanks ---
**Author:** ![xaprb](https://avatars.discourse-cdn.com/v4/letter/x/49beb7/32.png) [@xaprb](https://forums.percona.com/u/xaprb)\ **Post date:** [March 13, 2010, 4:31pm UTC](https://forums.percona.com/t/unable-to-restore-a-mysql-database-from-dump-produced-by-mysqldump/1361/2 "2010-03-13T16:31:17Z")
Is it done yet? The short answer is, don’t use mysqldump for really big tables. ---
**Author:** ![kostagr33k](https://avatars.discourse-cdn.com/v4/letter/k/ebca7d/32.png) [@kostagr33k](https://forums.percona.com/u/kostagr33k)\ **Post date:** [March 31, 2010, 3:56pm UTC](https://forums.percona.com/t/unable-to-restore-a-mysql-database-from-dump-produced-by-mysqldump/1361/3 "2010-03-31T15:56:00Z")
Any explanation as to why not to use mysqldump on large tables? Any good alternatives for both innodb and myisam tables? Kosta