Near keyword in Full Text Search SQL server 2005

We've migrated to SQL 2005 and we are seeing that AND and NEAR opertors are
returning exactly the same results, this behavior did not occur in SQL 2000.
example:
select count(*) from table1 where contains(*,'foo near bar') = 2494
select count(*) from table1 where contains(*,'"foo" and "bar"') = 2494
I have tried all of the syntax options I could find and am also able to
provide examples where foo and bar are quite far apart (~3000 characters) fa
r
more than 50 words I've seen quoted for 2005. Appreciate if anyone has any
ideas on why. Do I need to change some setting in the SQL Server?
ThanksI reported this as a bug to Microsoft some time ago, and I was told that
this behavior is by design due to a customer request. Here is my original
post.
http://groups.google.com/group/micr...a0?dmode=source
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"so3" <so3@.discussions.microsoft.com> wrote in message
news:31E328D2-CB77-47A1-9B19-A319DBE29320@.microsoft.com...
> We've migrated to SQL 2005 and we are seeing that AND and NEAR opertors
> are
> returning exactly the same results, this behavior did not occur in SQL
> 2000.
> example:
> select count(*) from table1 where contains(*,'foo near bar') = 2494
> select count(*) from table1 where contains(*,'"foo" and "bar"') = 2494
> I have tried all of the syntax options I could find and am also able to
> provide examples where foo and bar are quite far apart (~3000 characters)
> far
> more than 50 words I've seen quoted for 2005. Appreciate if anyone has
> any
> ideas on why. Do I need to change some setting in the SQL Server?
> Thanks|||I reported this as a bug to Microsoft some time ago, and I was told that
this behavior is by design due to a customer request. Here is my original
post.
http://groups.google.com/group/micr...a0?dmode=source
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"so3" <so3@.discussions.microsoft.com> wrote in message
news:31E328D2-CB77-47A1-9B19-A319DBE29320@.microsoft.com...
> We've migrated to SQL 2005 and we are seeing that AND and NEAR opertors
> are
> returning exactly the same results, this behavior did not occur in SQL
> 2000.
> example:
> select count(*) from table1 where contains(*,'foo near bar') = 2494
> select count(*) from table1 where contains(*,'"foo" and "bar"') = 2494
> I have tried all of the syntax options I could find and am also able to
> provide examples where foo and bar are quite far apart (~3000 characters)
> far
> more than 50 words I've seen quoted for 2005. Appreciate if anyone has
> any
> ideas on why. Do I need to change some setting in the SQL Server?
> Thanks