Textpattern CMS support forum
You are not logged in. Register | Login | Help
- Topics: Active | Unanswered
#13 2008-05-15 17:05:15
- redbot
- Plugin Author
- Registered: 2006-02-14
- Posts: 1,410
Re: man oh man. migrating to local site headaches.
Er… sorry, I can try with a last suggestion then I hope someone more experienced than me can help you.
As far as I know the number of tables can vary if you installed some plugins (for example hak_tinymce or glz_custom_fields) so I’m wondering if your 15th table is maybe a gigantic “txp_log” table.
In your live server, with phpadmin, have you tried to check how big is that table? If it’s too big you can safely export all your tables minus the “txp_log” table and proceed as usual…
Last edited by redbot (2008-05-15 17:06:12)
Offline
Re: man oh man. migrating to local site headaches.
just to update this problem: i’ve found that the site i’m having problems with migrating seems to have a unique problem with the SQL file. i tried it with another one of my sites and it was very quick and easy.
so how can i make sure i’m getting a clean SQL export?
anyone had this problem before?
it worries me cause theoretically my backups of the site are no good.
Offline
#15 2008-07-02 19:17:30
- els
- Moderator
- From: The Netherlands
- Registered: 2004-06-06
- Posts: 7,458
Re: man oh man. migrating to local site headaches.
mrtunes wrote:
i tried it with another one of my sites and it was very quick and easy.
If you’re doing it exactly the same way for the ‘problem site’, at least you know you’re not making mistakes.
still trying to work around the mysql import timing out
I’ve had this once before when trying to import a Slimstat database, one table in there was huge… the txp_log table can be rather large as well.
In the import screen in my phpMyAdmin I see something like Maximum size: 2.048KB. Could it be that your sql file is too large?
Offline
Re: man oh man. migrating to local site headaches.
Els wrote:
I’ve had this once before when trying to import a Slimstat database, one table in there was huge… the txp_log table can be rather large as well.
In the import screen in my phpMyAdmin I see something likeMaximum size: 2.048KB. Could it be that your sql file is too large?
the site that was easy to import was 1.5 megs. my problem site is 4-5 megs depending on which sql i use. one came from the RSS DB plugin
Offline
#17 2008-07-02 19:48:34
- els
- Moderator
- From: The Netherlands
- Registered: 2004-06-06
- Posts: 7,458
Re: man oh man. migrating to local site headaches.
Hmm… the 2,048KB I mentioned is my local install. Most hosts indicate 50 or 60MB, so 4-5 could hardly be a problem I’d think.
Have you tried exporting and importing the tables one by one (so each table is a separate file)?
Offline
Re: man oh man. migrating to local site headaches.
Els wrote:
Hmm… the 2,048KB I mentioned is my local install. Most hosts indicate 50 or 60MB, so 4-5 could hardly be a problem I’d think.
Have you tried exporting and importing the tables one by one (so each table is a separate file)?
my localhost phpmyadmin says: Max: 16,384 KiB
so i tried Gzipping which brought the 5meg database down to like 700kb
tried the import and got one of my usual style errors:
Fatal error: Maximum execution time of 300 seconds exceeded in C:\xampp\phpMyAdmin\libraries\import\sql.php on line 129
i guess it’s time to try the one-by-one advice you gave which sounds similar to when i got my wisdom teeth pulled. ;)
Last edited by mrtunes (2008-07-02 21:02:46)
Offline
Re: man oh man. migrating to local site headaches.
it turns out that the Log table was the culprit. i didn’t realize how large the log can get, and i’m sure it slows down site performance a lot. so i deleted all 8 pages of logs(100/page), turned logging off. exported my sql file and it imported into localhost fine now :)
i spent a lot of time on this so i’m glad it’s resolved now. but what i’m confused about is my other site that i transferred the sql successfully before, had 300 less logs
Offline