Re: help tuning query

Posted in 2010

Floyd Wellershaus — Fri, 21 May 2010 08:05:47 -0500 (CDT) — source: Usenet: comp.databases.informix

Excellent point Obnoxio. I did this. It runs much qucker ( like only 28 seconds as opposed to 7 minutes ) because it's doing a dynamic hash join It seems to provide the same info, however in a different order. Not sure if it's really the same query anymore. SELECT t1.token as __token, t1.first_name AS firstName, t1.initial as middleInitial, t1.last_name as lastName, substr(t1.street1,1,8) as streetAddress, t1.birth_dt as dateOfBirth FROM s701362 t1,s701362 t2 WHERE NVL(UPPER(t1.first_name),'') = NVL(UPPER(t2.first_name),'') AND NVL(UPPER(t1.last_name),'') = NVL(UPPER(t2.last_name),'') AND NVL(UPPER(t1.initial),'')= NVL(UPPER(t1.initial),'') AND NVL(UPPER(substr(t1.street1,1,8)),'')=NVL(UPPER(substr(t2.street1,1,8)),'') AND NVL(t1.birth_dt,'')=NVL(t2.birth_dt,'') AND t1.token in (select __token token from s701362_er t1 where t1.warn_id='86') ----- Original Message ----- From: obnoxio@serendipita.com Sent: Fri, May 21, 2010, 7:00 AM Subject: Re: help tuning query Floyd Wellershaus wrote: