RE: Indexing problem with UTF8 in 4.1.4?

2004-09-30 Thread Kevin Cowley
> -Original Message- > From: Harald Fuchs [mailto:[EMAIL PROTECTED] > Sent: 30 September 2004 12:16 > To: [EMAIL PROTECTED] > Subject: Re: Indexing problem with UTF8 in 4.1.4? > > In article > <[EMAIL PROTECTED]>, > Kevin Cowley <[EMAIL PROTECTED]>

Re: Indexing problem with UTF8 in 4.1.4?

2004-09-30 Thread Harald Fuchs
In article <[EMAIL PROTECTED]>, Kevin Cowley <[EMAIL PROTECTED]> writes: > If I knew why I wouldn't be asking. Now by our reconing the key of the > fields is 343 bytes, encoding in UTF8 makes that key 343 bytes Not 1000 > since under utf8 each character is encode in 8 bits. What makes you think s

RE: Indexing problem with UTF8 in 4.1.4?

2004-09-29 Thread Kevin Cowley
Kevin Cowley R&D Tel: 0118 902 9099 (direct line) Email: [EMAIL PROTECTED] Web: http://www.alchemetrics.co.uk > -Original Message- > From: gerald_clark [mailto:[EMAIL PROTECTED] > Sent: 29 September 2004 17:29 > To: Kevin Cowley > Cc: [EMAIL PROTECTED] > Subject

Re: Indexing problem with UTF8 in 4.1.4?

2004-09-29 Thread gerald_clark
Kevin Cowley wrote: Running 4.1.4 with a database that has a default encoding of UTF8 If we execute the following we get an error. CREATE TABLE idxbe_resident ( urn INT UNSIGNED NOT NULL, keyAddress_Part1 CHAR(5) BINARY NOT NULL, dataPerson_Name CHAR(60), dataAddress_Part1 CHAR(140), dataAddress_P

Re-indexing problem on large table

2003-10-20 Thread gunnar . lunde
Hello! I hope someone can help us with a problem we have: We had a table that was 35G big and the index file was about 16G (ca 120 million records). We ran into a problem where the database produced an "no more room in index file" error. To fix this we regenerated the table and set max_rows t

RE: Indexing Problem

2001-10-26 Thread Wai Lee
umn I use is VARCHAR(40), and I am not sure when I use create index idx1 on transaction(vendor_id(20)); will help??? -Original Message- From: Sergei Golubchik [mailto:[EMAIL PROTECTED]] Sent: Friday, October 26, 2001 10:53 AM To: Wai Lee Cc: [EMAIL PROTECTED] Subject: Re: Indexing Prob

Re: Indexing Problem

2001-10-26 Thread Sergei Golubchik
Hi! On Oct 26, Kyle Hayes wrote: > On Friday 26 October 2001 07:18, Wai Lee wrote: > > > I dig through the manual and changed any possible settings > > > > set-variable= max_heap_table_size=2000M > > set-variable= key_buffer=2500M > > set-variable= max_allowed_packet=1M > > set-varia

Re: Indexing Problem

2001-10-26 Thread Fournier Jocelyn [Presence-PC]
Hi, Your record_buffer and sort_buffer seem far too high. Don't forget MySQL could eat up ((sort_buffer + record_buffer) * max_connections + key_buffer) Mo of memory. Even with a max_connections set to 1, MySQL could eat in your case up to 7 Go of memory =) - Original Message - From: "

Re: Indexing Problem

2001-10-26 Thread Kyle Hayes
On Friday 26 October 2001 07:18, Wai Lee wrote: > I dig through the manual and changed any possible settings > > set-variable= max_heap_table_size=2000M > set-variable= key_buffer=2500M > set-variable= max_allowed_packet=1M > set-variable= table_cache=512 > set-variable= sort_

Re: Indexing Problem

2001-10-26 Thread Sergei Golubchik
Hi! On Oct 26, Wai Lee wrote: > Hi all, > > Can someone tell me how to speed up the index creation??? > > I am trying to build an index for a 13,875,354 records(13 million) table > with 176,322 distinct vendor_id(VARCHAR(40)) in the table. > > the existing size of the transaction table: > tran

Re: Indexing problem with large database

2001-05-25 Thread ryc
With the correct indexes this query should run in less than a second. Basically what you should do is make an index for every column that is used in the where clause. For instance, if you had a query ... WHERE A=X AND B=Y AND C=Z (A,B,and C are in the same table) you would create an index (A,B,C)