My database is over quota...? - Page 2 My database is over quota...? - Page 2
 

News:

CPG Release 1.6.27
change DB IP storage fields to accommodate IPv6 addresses
remove use of E_STRICT (PHP 8.4 deprecated)
update README to reflect new website
align code with new .com CPG website
correct deprecation in captcha

Main Menu

My database is over quota...?

Started by VIPguard, December 17, 2008, 09:16:38 AM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

Joachim Müller

The show stopper probably is the stats table. You shouldn't have enabled stats recording in the first place if you have no idea on the impact. You should have emptied the stats on a scheduled basis. Ranting about the size of the exif table is invalid as well.

Now stop whining and do as suggested:
  • Turn of the recording of detailed stats in coppermine's config
  • Turn off the population of exif information in coppermine's config
  • Backup your entire database using phpMyAdmin or mySqlDunmper. If you have no idea how to accomplish that: hire a freelancer or ask your webhost for support -> no support from us
  • Empty (not delete!) the table that contains your stat details using phpMyAdmin. Do not delete the entire database - just empty the table! If you have no idea how to accomplish that: hire a freelancer or ask your webhost for support -> no support from us
  • Empty (not delete!) the table that contains your exif data using phpMyAdmin. Do not delete the entire database - just empty the table! If you have no idea how to accomplish that: hire a freelancer or ask your webhost for support -> no support from us

This thread looks like a parody of the bad joke of the type "Help, doctor: whenever I hit myself on the head with a baseball bat it hurts so badly". You know what the doctor will reply: "well, then don't hit yourself in the first place". :D