Hi
How much data (realistically) can a MySQL database handle?
I've got a *big* mysql database that is currently offline, the main table has circa 1.5 Million rows and I want to use this @ some point in the near future to drive a website.
Now I've used MySQL loads of times before on web projects without any complaints from the server and it's always been sweet, however, a DB as large as this
is taking me into new territory. Also I need to write a script to index the big table for keywords to assist in searching, so I'm probably gonna end up with 2 *big* tables.
If you people feedback to me and say that MySQL can handle this, what other things should I take into consideration?
For example:
=on launch the website won't be getting a lot of hits, so connections won't be an issue (immediately) but I want the thing to be scaleable and moving it will be a pain.
=the DB will sit on my dedicated webserver, but it also acts as a (small) mailserver and runs one other site (back-end.org) that gets circa 40K page impressions per month.
=The machine is a 500MHz PII with only 64MB Ram, should I upgrade this?
I hope this makes sense, basically, can MySQL deal with a big DB (is this big?) running a site getting say 1 million hits [pages] per month and if so, does it need to be running on it's own machine (without Apache etc)
tia
Bealers
How much data (realistically) can a MySQL database handle?
I've got a *big* mysql database that is currently offline, the main table has circa 1.5 Million rows and I want to use this @ some point in the near future to drive a website.
Now I've used MySQL loads of times before on web projects without any complaints from the server and it's always been sweet, however, a DB as large as this
is taking me into new territory. Also I need to write a script to index the big table for keywords to assist in searching, so I'm probably gonna end up with 2 *big* tables.
If you people feedback to me and say that MySQL can handle this, what other things should I take into consideration?
For example:
=on launch the website won't be getting a lot of hits, so connections won't be an issue (immediately) but I want the thing to be scaleable and moving it will be a pain.
=the DB will sit on my dedicated webserver, but it also acts as a (small) mailserver and runs one other site (back-end.org) that gets circa 40K page impressions per month.
=The machine is a 500MHz PII with only 64MB Ram, should I upgrade this?
I hope this makes sense, basically, can MySQL deal with a big DB (is this big?) running a site getting say 1 million hits [pages] per month and if so, does it need to be running on it's own machine (without Apache etc)
tia
Bealers