Page 1 of 1

Old databases that are no longer required

Posted: Fri Sep 24, 2010 3:19 am
by mattgen21
Hello!

I'm using mysql 5 community server on a Windows2003 box (its a game server colo) to store dbs required by its cs/css/tf2 (custom counterstrike and half life 2) mods. I've since upgraded various plugins / mods where it was easier to create a new db and import the contents of the previous versions db, rather than attempting to alter / configure the outdated database used by previous mods. When the game developers release updates, it can sometimes adversely effect the mods I'm using and rolling back to a previous version is often a temporary solution.

My question is whether or not the databases that are no longer being used on my mysql server take up resources, other than hd space, when not being called/connected/queried by anything. For example, is it using physical memory space (not hdd) even when its not used? If so, is there a way for me to disable them, but not completely remove them from the mysql server? Is there a way to create a complete backup of the entire db and store it on hdd space elsewhere, but still have the ability to restore it in a relatively quick and painless manner?

Sorry if I'm not wording something right, I dont know a whole lot about the topic.

Re: Old databases that are no longer required

Posted: Fri Sep 24, 2010 5:07 am
by mattgen21
I just timed an export of one of the older dbs (I'm not quite sure how many rows/tables are in there, but its at 300Mb and still exporting) as an 'sql-script' using Toad for MySQL and its taking over an hour. I'll definitely want to either find a way to completely disable them so they do not initialize when the server starts or find a faster method to export/back them up. I do not have desktop / shell access to the server its being hosted on.

I figured any additional info would help in getting a reply. Thanks!

Re: Old databases that are no longer required

Posted: Fri Sep 24, 2010 12:11 pm
by John Cartwright
I'm far from an expert on database innards, especially other than MySQL. However, your database will consume resources regardless, since it will load data into memory to quickly perform look-ups (which is why you want more RAM than your database size).