How large? Any precaution for a large db?

[T.A.C. One]

I have to handle a very big (~50 gigabyte) database (quite all in a
table), and I am going to use mysql.

Can mysql handle all that ammount of data?

What problems I am going to have?
Should I take any precaution?

Is some other database-engine more suitable for this work?
Posgresql maybe?

Thx in advance

Tac

[Aggro]

T.A.C. One wrote:

I have to handle a very big (~50 gigabyte) database (quite all in a
table), and I am going to use mysql.

Can mysql handle all that ammount of data?
If operating system can handle files large enough for the need, then
MySQL should handle it as well.
What problems I am going to have?
Should I take any precaution?
Well with that amount of data I'm sure you are using indexes, if you are
not, you will be soon ;) .. You might need to check your backup plans
also, because it's not very easy and fast to backup that kind of data
amounts.
Is some other database-engine more suitable for this work?
Posgresql maybe?

If you are not tied to Windows, then Postgresql gives very good
alternative to MySQL. IMHO Postgresql is better for large database
systems while MySQL suits better for small database systems. But nothing
stops you from using either one for all the cases.

[Robert Morgan]

Hi,

I have a MySQL DB which currently weighs in at around 200MB and will
be up in the GBs before long. It serves two purposes, collecting
transaction data and enabling reporting on that data.

More complex queries tend to run quite slowly. I've indexed the
appropriate columns which has sped things up a lot, however I notice
from running 'top', that when running such a query, MySQL grabs a good
99.9% of the CPU time.

As the DB gets larger and the site busier, am I going to be wise to
perhaps offload daily transaction data into a separate reporting DB,
preferably on a separate box, and keep the transaction DB small and
lean? Or would this be unnecessary, and provided I have enough HD
space / RAM / CPU power, I'll be OK?

Thanks in advance,

Rob