On 06/12/13 15:08, jeffrey Butera wrote:
Unidata 7.3.3 on RedHat: I have a table with numerous indicies built:
Since these are data fields (nothing computed on-the-fly) and indexed,
queries should be fast.The table has approximately 737,000 records.
This query runs in under 1 second:
Jeffrey,
And index is a B(Binary)+ tree, the plus means that it auto adjusts and
balances itself as it builds or shrinks.
After UniData 5.2 UniQuery will use as many indices as it can. In your case
it is the equivalent of doing two UniQuery selects to two different lists
and then doing a
Hi David:
In Unidata indexes DO mean faster selects. I have file with millions
of records with about 14 indexes and most every select on the index
comes back in under a second. Our disks are 90,000 IO's per second
with a 16GB main memory, without indexes to select and read through
that data
In Unidata indexes DO mean faster selects. I have file with millions
of records with about 14 indexes and most every select on the index
comes back in under a second. Our disks are 90,000 IO's per second
with a 16GB main memory, without indexes to select and read through
that data takes 5 to 10
-boun...@listserver.u2ug.org] On Behalf Of Doug Averch
Sent: Friday, December 06, 2013 9:13 AM
To: U2 Users List
Subject: Re: [U2] Unidata index/query ?
Hi David:
In Unidata indexes DO mean faster selects. I have file with millions of
records with about 14 indexes and most every select on the index
Maybe I am just old school but I would put another WITH in the line after the
AND.
-Original Message-
From: u2-users-boun...@listserver.u2ug.org
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of jeffrey Butera
Sent: Friday, December 06, 2013 7:09 AM
To: U2 Users List
Subject: