SQL Query tuning WITH in, not in, like

Question

is there any alternative can i user for in, not in, like to optimize this sql statement.
SELECT TKTNUM||’~’||
CUSNAME||’~’||
DECODE(PRTY,0,’PRIORITY 00’, 1,’PRIORITY 01’ ,2,’PRIORITY 02’, 03,’PRIORITY 03’, 04,’PRIORITY04’,’OTHERS’) ||’~’||
TO_CHAR(NEW_TIME(CREATEDTTM,’GMT’,’&2’),’MM-DD-YYYY HH24:MI:SS’) ||’~’||
CURSTA||’~’||
CURSTS||’~’||
OTGTM||’~’||
TOPGRPNAME||’~’||
TO_CHAR(NEW_TIME(LASTUPDDTTM,’GMT’,’&2’),’MM-DD-YYYY HH24:MI:SS’) ||’~’||
RIM(REPLACE(REPLACE(PROBSUMMARY,’’,’’),CHR(10),’’||’~’
FROM T3TKTHEADER
WHERE
CURSTA NOT IN(‘RESOLVED’,’CLOSED’)
AND TOPGRPNAME IN(‘CASJC.OPS’,EMEA.WTO’,’INCHN.GSD-DBA’)
AND PRIT IN (‘0’,’1’,’2’)
AND CUSNAME NOT LIKE ‘% VANGENT%’
ORDER BY PRTY, CREATEDTTM DESC

Answer 1

Hi,
Welcome to the forum!
998537 wrote:
is there any alternative can i user for in, not in, like to optimize this sql statement.That depends on what you mean by "optimize".
There are lots of other ways to get the same results. For example
AND        prit          IN ('0', '1', '2')is equivalent to
AND       (    prit     = '0'
       OR   prit     = '1'
       OR   prit     = '2'
       )and
AND        cusname      NOT LIKE '% VANGENT%'is equivalent to
AND       INSTR (cusname, ' VANGENT')     = 0Some people might have a personal preference for these (or other) alternate forms. I don't; I find what you posted easier to understand and maintain. I would suggest you format your code, however.
Do you want it to run faster? See {message:id=9360003}
If you have some very particular requirements and data, then function-based indexes might help.
For example, if you often look for those same 3 values of prit, and, taken together, they account for less than 5% of the rows in the table, then a function-based index might make things faster. There's nothing in what you posted that looks espcially likely, however.