Re: SQL tuning with LIKE expression

From: Niall Litchfield <n-litchfield_at_audit-commission.gov.uk>
Date: Tue, 23 Sep 2003 15:23:11 +0100
Message-ID: <3f70574f$0$15782$ed9e5944@reading.news.pipex.net>

"Junaid" <letsconnect_at_hotmail.com> wrote in message news:dfb44909.0309230613.4e152375_at_posting.google.com...
> Sybrand Bakker <gooiditweg_at_sybrandb.demon.nl> wrote in message
news:<83numvo78k3kn3tta6tgci6ljjs3pahv8n_at_4ax.com>...
> > On 22 Sep 2003 09:43:22 -0700, letsconnect_at_hotmail.com (Junaid) wrote:
> >
> > > For utility purposes, I have to use the like expression in the where
> > >clause.
> >
> > No, you don't. There is no reason to use LIKE on a number column.
> >
> >
> > Sybrand Bakker, Senior Oracle DBA
> >
> > To reply remove -verwijderdit from my e-mail address
>
> I know I don't have to but our shared client application's framework
> is forcing us to use it, for the time. Also, if I use numeric operator
> for this number column, only = utilizes the index on this column. If I
> use < or > then the associated index is not used.
>
> Any ideas?

As far as numeric operators are concerned a) Do you have up to date stats? and
b) what percentage of the table are you expecting to return?

As far as being forced to use like then the framework is forcing you to utilize a FTS.

-- 
Niall Litchfield
Oracle DBA
Audit Commission UK

Received on Tue Sep 23 2003 - 09:23:11 CDT