Warning: This message has had one or more attachments removed
Warning: (not named).
Warning: Please read the "AngelicHost-Attachment-Warning.txt" attachment(s)
for more information.

Bill;

We use them all the time. They make a huge difference (especially on the
older, slower systems).

I don't know about the exact alternate key thing. I use the below format and
it works things come back quickly. It's the other way that doesn't work
(SELECT NAMES WITH INDEX_1 = "[JOHN").

It does take longer if there is a large data set to return.

I just tried it on both UD 6.0.12 and 7.1.5PE.

Problems I've seen with an index:
1. early 5 version had a bad udtsort.exe and the index was not built properly
2. file being actively updated when the index was built
3. index was created but not actually built.
4. bad characters in the data (not so much a problem with the index)

Deleting the index (making sure the x_ file is gone in the OS) and recreate
and rebuild has always solved the problems. Note that we don't usually do
"text searches" like this. We generally use the index for client numbers,
timekeepers, fiscal period, invoice etc. Our application started on Pick
before they had indexes so we have our own cross-reference file for text
searches. We also don't have *really* large files. 99% are under the 2GB
threshold and only a handful of clients have anything larger. I think the
largest is around 4-5GB and I use the index on it all the time - really fast.

Sorry this wasn't much help.
Colin Alfke
Calgary Canada

________________________________

From: Bill Haskett

I've been having problems getting UniQuery to use defined (and built) indexes
in
UniData.  IBM has informed me that UniQuery does not use indexes unless the
exact
alternate key is used.  e.g.

:SELECT NAMES WITH INDEX_1 = "JOHNS]"
                         or
:select NAMES WITH INDEX_1 LIKE "JOHNS..."

...does not use the index.  IBM says using:

:SELECT NAMES WITH INDEX_1 = "JOHNSON, RON"

...will work.  However, this doesn't work on my system (UD v7.1.9).  All of my
index
testing works fine in UniVerse, i.e. Retrieve selections use the defined
indexes and
returns all selects immediately.

Does UniQuery use indexes in UniData?

Thanks,

Bill
This is a message from the MailScanner E-Mail Virus Protection Service
----------------------------------------------------------------------
The original e-mail attachment "winmail.dat"
was believed to be infected by a virus and has been replaced by this warning
message.

If you wish to receive a copy of the *infected* attachment, please
e-mail helpdesk and include the whole of this message
in your request. Alternatively, you can call them, with
the contents of this message to hand when you call.

At Thu Aug 30 20:35:02 2007 the virus scanner said:
   Could not parse Outlook Rich Text attachment

Note to Help Desk: Look on the AngelicHost MailScanner in
/home/virtual/site2/fst/var/spool/mail.quarantine/20070830 (message
l7V3Z0Ks003173).
--
Postmaster
MailScanner thanks transtec Computers for their support
-------
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/

Reply via email to