Translating with DrWatson… this can take a few seconds the first time.
This is a genuine, complex translation. DrWatson protects commands, error codes, and log output while naturally translating the surrounding text. It’s translated once and saved.
Nils Myklebust — — source: Informix-list mailing list archive (1991-1998)
On Thu, 30 Apr 1998 10:32:41 -0400, Steve Romankiw
<sromankiw@execrisk.com> wrote:
>
>We are running ODS 7.23 on Solaris 2.5.1. There are times when queries
>like the one below need to be performed.
>
>SELECT * FROM employee
>WHERE address like "%SEQUENTIAL%">
>Although this is a very simple query, it is VERY expense to run. The
>optimizer is forced into doing a seq scan.
>
>What approaches have you taken to search the character strings inside of
>character fields?
Our users do this sometimes but then they know they have to wait quite
some time for the result. I know of no good solution. One thing you
can do is to fragment the table over many disks. It would still search
the entire table, but could potentially do it in parallel on all
disks.
Nils Myklebust
NM Data AS
Norway
E-mail: Nils.Myklebust@nmdata.com
FAQ at: http://www.iiug.org/techinfo/faq/faq_top.html
(Now with ODBC info under "Third party products".)
We use strictly necessary cookies to make this site work. With your
consent we’d also use optional cookies for analytics and marketing. You can accept all,
reject all, or choose. Read our Cookie Policy.