Subject: SV: [U2] [u2][ud] Poor select performance
Sorry, that didn't help...
Thanks anyway
Bjvrn Eklund
-Ursprungligt meddelande-
Fren: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Perry Taylor
Skickat: den 10 februari 2006 15:07
Till: u2-users@listserver.u2ug.org
Dmne: RE: [U2] [u
OTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Jerry Banker
> Sent: Friday, February 17, 2006 2:13 PM
> To: u2-users@listserver.u2ug.org
> Subject: Re: [U2] [u2][ud] Poor select performance
>
> I selected 311000 records on our new Linux Dell 6800 server
> and it took 5 se
ECTED]>
To:
Sent: Friday, February 17, 2006 1:58 PM
Subject: RE: [U2] [u2][ud] Poor select performance
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
[EMAIL PROTECTED]
Sent: Friday, February 10, 2006 6:09 AM
To: u2-users@listserver.u2ug.org
Subject: [U2]
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
[EMAIL PROTECTED]
Sent: Friday, February 10, 2006 6:09 AM
To: u2-users@listserver.u2ug.org
Subject: [U2] [u2][ud] Poor select performance
[snip]
Selecting a customer with 570 000 records can take 30 seconds.
Bjvrn
Oh yes - some reasonably recent enhancements in UniData processing of joins
makes it worth re-checking any SELECTs with joins against a current
version...
Regards
JayJay
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
Bjvrn
You should aim for a key structure that avoids "overloading" a single key
value with records and at the same time gives you a good hit rate.
Typical problem areas (though not yours in this case) are keys of 0 and 1,
or with high numbers of null (empty) string entries.
If you can post some
Try building an index on the whole filed and using a RANGE selection ...
i.e. >= and <=
Let us know how it goes - it may do the job. Remember to use no.dups and
no.nulls for a bit more pep
(pattern matches can't use the index)
Regards
JayJay
-Original Message-
From: [EMAIL PR
My pet peeve with Universe Indexes is in selecting multiple values of an
indexed field
The following select might take 10 minutes
SELECT CONTRACT WITH I_CONTRACT = "50178227" "50092158" "50006089"
"50178228" "50092159" "50006090" "50178229" "50092160" "50006091"
"50178230"
Whereas SELECT CONTRA
Out of interest, how long does the selection take without the index?
Regards,
Rob Wills
(rob dot wills at tigerinfotech dot com)
Martin Philips wrote on 10/02/2006 14:04:26:
> Given the number of records that you say are in the file, you are
probably
> going to visit most groups anyway so the
My experience is with UniVerse but I suspect it would suffer from the
same thing. It's likely the problem is the high number of records per
customer number. You might try indexing the entire key then doing a
select on the customer number portion. Something like this maybe (not
sure of the UniDat
> Selecting other indexed values in the same file which gives me 5 records
out
> of the 5 million is very very fast.
30 second certainly sounds excessive but an index entry leading to over
500,000 records is not a good idea. To be effective, an index needs to lead
you to a very small proportion of
11 matches
Mail list logo
