Re: incorrect query reults

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: John Kane (jt-kane_at_comcast.net)
Date: 11/16/04 

Date: Tue, 16 Nov 2004 01:12:28 -0800

Thanks, Gerald,
Could you proved the exact text from a few of the rows that contain the
string 'oenorm', including all punctuation characters?
Is this HTML code or plain text that is stored in a text or varchar column?
Also, what is the language of the text stored in the column?

All of these factors, when considered with the OS platform (in your case
Win2K) can affect the results from the CONTAINS query.

Regards,
John

"Gerald Baeck" <exc3ktest@hotmail.com> wrote in message
news:ac510211.0411152308.3ec64f25@posting.google.com...
> John,
>
> its the other way round. The CONTAINS-Query returns many rows and the
> LIKE-Query does not. The LIKE-QUery return the correct resultset in
> that case.
>
> thx, Gerald.
>
>
> "John Kane" <jt-kane@comcast.net> wrote in message
news:<OtWs$f1yEHA.3656@TK2MSFTNGP09.phx.gbl>...
> > Gerald,
> > Why would you expect contains(text, ' "oenorm*" ') to return results
when
> > using text like '%oenorm%' does not return results?
> > While often the T-SQL LIKE will return different results when compared
to
> > CONTAINS or FREETEXT, but if T-SQL LIKE cannot find it with it's
"pattern
> > matching" method and using leading and trailing wildcards (%), then most
> > likely CONTAINS or FREETEXT will not return results as well as the
search
> > string is most likely not in your column: text.
> >
> > Regards,
> > John
> >
> >
> >
> >
> >
> >
> >
> > "Gerald Baeck" <GeraldBaeck@discussions.microsoft.com> wrote in message
> > news:418794BC-8ED0-4B72-9CC7-0AF3C50C04F5@microsoft.com...
> > > I forgot to tell, that the query
> > >
> > > select id, url from queue_suchsourceindex
> > > where text like '%oenorm%'
> > >
> > > returns no rows, as it should.
> > >
> > > thx, Gerald.
> > >
> > >
> > > "Gerald Baeck" schrieb:
> > >
> > > > Hi,
> > > >
> > > > another problem occured!-)
> > > >
> > > > I did the following SQL-query:
> > > >
> > > >
> > > > select * from queue_suchsourceindex
> > > > where contains(text, ' "oenorm*" ')
> > > >
> > > > But in the result there are many rows, that do not contain the word
> > "oenorm"
> > > > in its text field. First i thought i mixed somethiong up in
Application,
> > but
> > > > everything is working right there. Just the query return the wrong
> > results.
> > > >
> > > > I have no clue, how to find out what the problem is.
> > > >
> > > > thx in advance, Gerald.
> > > >
> > > > my configuration:
> > > > Microsoft SQL Server 2000 - 8.00.760 (Intel X86) Dec 17 2002
14:22:05
> > > > Copyright (c) 1988-2003 Microsoft Corporation Enterprise Edition on
> > Windows
> > > > NT 5.0 (Build 2195: Service Pack 4)
> > > >
> > > >

Relevant Pages

  • Re: incorrect query reults
    ... the couple of incorrect hits with "oenorm*". ... "John Kane" wrote: ... >> regards, Gerald. ...
    (microsoft.public.sqlserver.fulltext)
  • Re: IRDA support
    ... >> Dear John, ... And I am using the same irda hardware! ... >> Regards, ...
    (microsoft.public.windowsxp.embedded)
  • Re: incorrect query reults
    ... switching to the neutral wordbreaker solved the problem. ... thx very much, Gerald. ... "John Kane" wrote: ... OENORM is not a true German word. ...
    (microsoft.public.sqlserver.fulltext)
  • Re: Printing Emails - Changing Fonts
    ... >>> Your friend sends you detailed instructions on how to repair your ... >>> television/car/washing machine. ... >>> Regards, ... >>> John. ...
    (microsoft.public.windows.inetexplorer.ie6_outlookexpress)
  • Re: Delete
    ... Regards ... John ... rather than allenbrowne at mvps dot org. ... >> If I comment out the SetWarnings Statement the record is deleted but I am ...
    (microsoft.public.access.formscoding)