Re: Bug related to large tables and it's indexes on Win2k

2002-06-05 Thread Keith C. Ivey
On 5 Jun 2002, at 7:50, Jared Richardson wrote: > This table is part of a product that contains publicly available (and > always expanding) publicly avilable biological data in addition to > large companies internal data. A one terrabyte cap very well could > come back to haunt us one day! (sadl

Re: Bug related to large tables and it's indexes on Win2k

2002-06-05 Thread Jared Richardson
- Original Message - From: "Keith C. Ivey" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Cc: "Jared Richardson" <[EMAIL PROTECTED]> Sent: Tuesday, June 04, 2002 5:24 PM Subject: Re: Bug related to large tables and it's indexes on Win2k | On 4

Re: Bug related to large tables and it's indexes on Win2k

2002-06-04 Thread Keith C. Ivey
On 4 Jun 2002, at 15:43, Jared Richardson wrote: > | >AVG_ROW_LENGTH=4096 MAX_ROWS=4294967295; > | > | Why do you use AVG_ROW_LENGTH=4096? It seems to me the max record | > length is 528...? | > > According to the MySql docs, the max table size is AVG_ROW_LENGTH * > MAX_ROWS > > We were try

Re: Bug related to large tables and it's indexes on Win2k

2002-06-04 Thread Jared Richardson
I replied below - Original Message - From: "Roger Baklund" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, June 04, 2002 3:24 PM Subject: Re: Bug related to large tables and it's indexes on Win2k | * Jared Richardson | [...] | > CREATE TABLE Ic

Re: Bug related to large tables and it's indexes on Win2k

2002-06-04 Thread Jared Richardson
| Jared, I can't help solve your problem, but I'd be very interested if you | got an answer! | | Two suggestions though that may be of use: | 1) Make sure your indexes are healthy | 2) Try using a MERGE table Thanks! The indexes are the problem as I understand it... it appears that MySql is

Re: Bug related to large tables and it's indexes on Win2k

2002-06-04 Thread Roger Baklund
* Jared Richardson [...] > CREATE TABLE IcAlias( >IcAliasID BIGINT NOT NULL PRIMARY KEY, >mID VARCHAR(255) NOT NULL, >IcEntityID BIGINT NOT NULL, >IcTypeID SMALLINT NOT NULL, >IcDupSortID VARCHAR(255) NOT NULL, >INDEX mIDIdx (mID), >INDEX IcTypeIDIdx (IcTypeID), >IN

Re: Bug related to large tables and it's indexes on Win2k

2002-06-04 Thread Ian Gilfillan
bles for our application. > > - Original Message - > From: "Schneck Walter" <[EMAIL PROTECTED]> > To: "'Jared Richardson '" <[EMAIL PROTECTED]>; "Schneck Walter" > <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>; &g

Re: Bug related to large tables and it's indexes on Win2k

2002-06-04 Thread Jared Richardson
ed Richardson '" <[EMAIL PROTECTED]>; "Schneck Walter" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Tuesday, June 04, 2002 10:20 AM Subject: AW: Bug related to large tables and it's indexes on Win2k | Well, | | im not an exper

Re: Bug related to large tables and it's indexes on Win2k

2002-06-04 Thread Jared Richardson
t: AW: Bug related to large tables and it's indexes on Win2k | Hi, | | what table-typ do you use ? | | rg Walter | | -Originalnachricht- | Von: Jared Richardson | An: [EMAIL PROTECTED]; [EMAIL PROTECTED] | Cc: Jared Richardson | Gesendet: 04.06.02 14:17 | Betreff: Bug related to

Re: Bug related to large tables and it's indexes on Win2k

2002-06-04 Thread Jared Richardson
t;[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Cc: "Jared Richardson" <[EMAIL PROTECTED]> Sent: Tuesday, June 04, 2002 9:40 AM Subject: Re: Bug related to large tables and it's indexes on Win2k At 08:17 4/6/2002 -0400, Jared Richardson wrote: Hi, >

Bug related to large tables and it's indexes on Win2k

2002-06-04 Thread Jared Richardson
Hi all, When large tables are being addressed, we seem to have encountered a bug related to having large indexes on the table. We have several tables in our system that have reached 4 gigs in size. We altered the table definition to allow it to get larger... this is our current table creation s