Archiving Data

I would like to archive data that we no longer need on a regular
basics.
We will need to query it maybe once every three or four months.

I would like to move the data from Current_DB.mytable to
History_DB.mytable.

What happen with DB's that we hardly use?
How much resources MySQL assigns it?
Is there a way to make that History_DB dormant?

What other options We have?

Thank you all,

Bre-x

On Thu, 10 Jan 2008 11:43:49 -0800 (PST), Bre-x wrote:
> I would like to archive data that we no longer need on a regular
> basics.
> We will need to query it maybe once every three or four months.
>
> I would like to move the data from Current_DB.mytable to
> History_DB.mytable.
>
> What happen with DB's that we hardly use?

Dy definition, very little.

> How much resources MySQL assigns it?

The same amount of disk as if it were current and active. Essentially
zero CPU.

> Is there a way to make that History_DB dormant?

Don't use it. But that won't change the amount of disk it uses.

> What other options We have?

You could take dumps of the history DB with mysqldump, put the
dumps on a removable medium like a tape or CD, and then drop the DB.

But I'm lazy, and disk is cheap, so unless we're talking about tens or
hundreds of millions of rows in this history DB, I wouldn't bother. It's
easier to buy a big disk once than fuss with restoring, analyzing and
dropping data every few months.

--
45. I will make sure I have a clear understanding of who is responsible for
what in my organization. For example, if my general screws up I will not
draw my weapon, point it at him, say "And here is the price for failure,"
then suddenly turn and kill some random underling. --Evil Overlord List