By The AL on
I made a site for a company I worked at nearly three years ago. The last maintenance I did on the site was approximately one year ago. The last thing I did was an SQL dump, and the .sql file was about 2MB. I was called upon to do some stuff today, and when I did the dump again I was shocked at the change in size. The .sql file is now over 130MB! Is that in anyway normal for a Drupal site?
Comments
clear table watchdog, cache*
clear table watchdog, cache*
I figured it caching or similar
I went into PhpMyAdmin and ran the database optimizer. I then cleared the watchdog and sessions tables. I also checked caching and did what I could in the Drupal back admin. The SQL dump hasn't changed in size.
Any suggestions?
It is difficult to say what
It is difficult to say what is 'normal'. How much content is on the site, how many users etc? I regularly work with a db dump bigger than that from a large-ish site. If you have cleared the caches and other non-essential tables and checked the settings for logs etc then the db size is most likely coming from content. What do the node tables look like?
Content-wise, the site hasn't
I cleared the cache_name tables again. Looks like two of them didn't clear from before. The dump is now down to 11.39MB. I'm content.
Also check batch table size
Also check batch table size
________________________
Override, don't change!
Of the 120 tables, I don't
Of the 120 tables, I don't see any with "batch" in their name.
Sorry. I don't know whether
Sorry. I don't know whether there was this table in drupal 5.
I had the same problem with batch table in drupal 6.
________________________
Override, don't change!