> handling from 3M to 20M records/day with potentially a lot
> of processing, live inserts/ updates etc.
How many records do you forsee? (There are some things to look up in the
manual to give MySQL a hint at the total size of the table so it can
start using longer internal pointers.)
How big ar
On Sun, Oct 20, 2002 at 10:52:22PM -0700, Steven Roussey wrote:
>
> Other people can tell you more about replication and how it is
> different from clustering or load balancing. And you can use it for
> backup in a way too. It depends on your requirements though.
Yeah. And you can use replicatio
I need to come up with an intra-company system recommendation: We are looking
at a possibly huge system getting data from a LAN(No web-based app or
anything-in fact it will NOT be connected to the web)
handling from 3M to 20M records/day with potentially a lot of processing,
live inserts/ upda
]
Sent: 21 October 2002 00:00
To: [EMAIL PROTECTED]
Subject: Tips for LARGE system
I need to come up with an intra-company system recommendation: We are
looking
at a possibly huge system getting data from a LAN(No web-based app or
anything-in fact it will NOT be connected to the web)
handling from 3M
