Hi,
On Tuesday, December 7, 2004, at 03:07 PM, Klaus Berkling wrote:
On Dec 6, 2004, at 3:51 PM, Harrison Fisk wrote:
Hi,
On Monday, December 6, 2004, at 04:15 PM, Klaus Berkling wrote:
I beginning to use MySQL clustering abilities for a large records
keeping solution.
I have installed 4.1.7 wi
On Dec 6, 2004, at 3:51 PM, Harrison Fisk wrote:
Hi,
On Monday, December 6, 2004, at 04:15 PM, Klaus Berkling wrote:
I beginning to use MySQL clustering abilities for a large records
keeping solution.
I have installed 4.1.7 with the clustering components. The ndbd and
ndb_mgmd processes are ru
Hi,
On Monday, December 6, 2004, at 04:15 PM, Klaus Berkling wrote:
I beginning to use MySQL clustering abilities for a large records
keeping solution.
I have installed 4.1.7 with the clustering components. The ndbd and
ndb_mgmd processes are running. I can create the database and tables
usin
On Dec 6, 2004, at 1:53 PM, Joshua Beall wrote:
"Klaus Berkling" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
I have started to import our data. I gather from the manual that
tables
are stored in RAM. I am trying to import a database with 11 tables
with
about 7 million rows. If
> -Original Message-
> From: John McCaskey [mailto:[EMAIL PROTECTED]
> Sent: Monday, December 06, 2004 17:01
> To: Joshua Beall
> Cc: [EMAIL PROTECTED]
> Subject: Re: Clustering and a large database
>
>
> Yes, mysql clustering is a ram only database. It does
Yes, mysql clustering is a ram only database. It does not make sense to
use it if you have a very large database.
You can use master/slave functionality and use whatever table type you
like. But using the newer clustering technology you have no choice but
to use the ndb table type which is ram o
"Klaus Berkling" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> I have started to import our data. I gather from the manual that tables
> are stored in RAM. I am trying to import a database with 11 tables with
> about 7 million rows. If I follow the math in the manual, one row
