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.
Sally Woolrich — — source: Informix-list mailing list archive (1991-1998)
In article <Pine.SCO.3.91.950721073842.5736A-100000@pali>
pop116@ind.eunet.hu "programmer" writes:
>
> In our TEST DB the result of a joined query and SET EXPLAIN is INDEX PATH
> for the two tables. On our REAL enviroment this result is for one table
> is SEQUENTIAL SCAN, and for the other one is INDEX PATH. Is this normal ??
> The query is awful slow, maybe thatsway ??
The sequential scan will be why the query runs very slowly. Unless
(unlikely!) your test & live dbs are IDENTICAL (size of tables, indexes,
key distributions) there is nothing sinister about the same query producing
different QEPs.
Check the following:
i) Indexes are identical
ii) Run 'update statistics' on both dbs
Hope this helps!
--
============================================================================
Sally Woolrich | This mail contains my personal
sally@excelsis.demon.co.uk | views not those of my employer!
============================================================================
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.