Database Size

Read 8313 times
Wondering... is there a way to reduce the size of the database? We back it up daily, but right now the file is well over 1GB in size. Might there be a way to reduce this size with out affecting current accounts on the server?

Thanks in advance,
Lou
Hello kahfluie,

Depending on the number of accounts on your server and how long has the serve being running, a 1GB database may not be that big at all, and you may find that micro managing the database to save storage space may prove to be more difficult that dealing with a 1GB daily backup.

That said, if you want to go the micro managing way, first you'll have to determine which tables are using the most storage space, you can use the following query to find out:

SELECT table_name AS "Tables",
round(((data_length + index_length) / 1024 / 1024), 2) "Size in MB"
FROM information_schema.TABLES
WHERE table_schema = "$DB_NAME"
ORDER BY (data_length + index_length) DESC;

Usually, playbackstats_tracks and track_history are always the biggest ones, and there isn't much you can do about them, unless you are ok with deleting your customer's historical statistics data. However if you see "visitorstats_sessions" using a lot of space, you may need to follow the instructions at:

http://www.centova.com/en/faq/cast3/troubleshooting/centova_cast_statistics_pages_load_slowly_or_time_out

HTH
A setting to control how much "historic" data to store will be a great addition. With hundreds of accounts the database grows like crazy. We have to manually delete the data using SQL queries, which is not a good way to do thing - it's a chance that something can go wrong.
http://www.radioboss.fm - stream hosting
http://www.djsoft.net - radio automation software
This has been a problem for a while http://forums.centova.com/index.php?topic=3523.0
My Auto DJ
Orlando, FL USA
Quality SHOUTcast Hosting http://myautodj.com
SHOUTcast Widgets http://shoutcastwidgets.com
I've posted a reply with further details/instructions to the thread linked by My Auto DJ.  If any of my assumptions are wrong there, please correct me, but as far as I'm aware this always comes down to "pollution" in the visitorstats_sessions table.  (See thread for details.)