Dario,
Unfortunately, SQL FTS is not as flexible as dtSearch in regards to how near
one word is to another. Basically, "near" is hard-coded at a 50 word spread,
i.e., any word can be *near* any other word within 50 words. There are other
factors as well, such as paragraph stops (CR/LF), but in SQL Server 2000
this cannot be altered. This may or may not change in the future release of
SQL Serve 2005 (codename Yukon) that will be in public beta later this year.
Regards,
John
[quoted text, click to view] "Dario" <anonymous@discussions.microsoft.com> wrote in message
news:f91e01c43e45$50105650$a301280a@phx.gbl...
> Basically we are switching the full text engine from
> DTSearch to SQL FTS. In DTSearch there were an option to
> tell the engine how many words before and after to look
> for with the *NEAR* clause.
> On SQL FTS the number of words before and after the first
> one are much higher and the users are complaining about
> it.
>
> Regards
> Dario
>
>
> >-----Original Message-----
> >Dario,
> >Are you looking for info on how to "influence" the NEAR
> function or want to
> >know how NEAR determines how *near* the words are to
> each other? Could you
> >provide some examples SQL FTS queries using NEAR and
> what your interested in
> >achieving?
> >
> >Regards,
> >John
> >
> >
> >"Dario" <anonymous@discussions.microsoft.com> wrote in
> message
> >news:f2f401c43da2$e2e82f00$a501280a@phx.gbl...
> >> Is there a way to set up a value to teach the query to
> >> set up how much 'near' a word is respect another?
> >>
> >> Is there any other way to do it besides NEAR?
> >>
> >> Tnanks
> >
> >
> >.
> >