If you have a CLOB, performance of searches is going to suck if doing it directly at the DB level, if it's even possible....adding FTS to the field indexes the field with a lucene index (FTS flat file), and a query against that field doesn't go to the DB, instead it does the flatfile index search, which is significantly more efficient and quicker than a db search....
So...yes it's avoidable if you don't want to take advantage of the things that fts gives you....but your options of improving the effort with the DB when searching a CLOB are very limited... On Fri, May 10, 2019 at 7:07 AM Thomas Miskiewicz <[email protected]> wrote: > Is FTS avoidable? > > On May 10, 2019, at 3:03 PM, LJ LongWing <[email protected]> wrote: > > Would FTS help you in any way? I know it would help, but the question is > are you willing to make that change. > > On Fri, May 10, 2019 at 6:53 AM Thomas Miskiewicz <[email protected]> > wrote: > >> Hi All >> >> we had to increase the size of a char field to over 4000 with huge >> performance degradation when using this field for search. >> >> Does anyone know how to heal this? Would the Oracle 12 Text Option help? >> >> >> Thomas >> -- >> ARSList mailing list >> [email protected] >> https://mailman.rrr.se/cgi/listinfo/arslist >> > -- > ARSList mailing list > [email protected] > https://mailman.rrr.se/cgi/listinfo/arslist > > > -- > ARSList mailing list > [email protected] > https://mailman.rrr.se/cgi/listinfo/arslist >
-- ARSList mailing list [email protected] https://mailman.rrr.se/cgi/listinfo/arslist
