Re: SQL 2000 FTS - Different results between Win2k3 and Win2000
- From: Tim F <TimF@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 25 Feb 2009 10:04:01 -0800
Dan - we have made changes to the noise word files. What should I look in
them for that would cause the the behavior of "5.2*" not finding "5.2MM"?
You're right - we're not relying on "5*MM" - I just happened to notice it
when trying to see how the period (.) was being processed and whether that
was a word breaker. Thanks.
"Daniel Crichton" wrote:
Tim wrote on Wed, 25 Feb 2009 05:53:02 -0800:.
We have a SQL 2000 server on Win2000 that returns search results that
are expected, but the same search on Win2k3 returns unexpected
(incorrect) data.
Server 1 (returns expected results):
@@version = Microsoft SQL Server 2000 - 8.00.2039 (Intel X86) May 3
2005 23:18:38 Copyright (c) 1988-2003 Microsoft Corporation
Enterprise Edition on Windows NT 5.0 (Build 2195: Service Pack 4)
@@language = us_english
Server 2 (returns unexpected results):
@@version = Microsoft SQL Server 2000 - 8.00.2039 (Intel X86) May 3
2005 23:18:38 Copyright (c) 1988-2003 Microsoft Corporation
Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 2)
@@language = us_english
The indexed field being searched is a varchar(255) with a collation
setting of SQL_Latin1_General_CP850_BIN. The value being sought in
that field is:
CARB 5.2MM 4X8 HONEY BINGO BIRCH LAUAN PANELING
The script used to search is:
select [KEY],p.ProductName from
CONTAINSTABLE(Product,ProductName,'"5.2*"')
inner join Product p (nolock) on p.ProductNumber = [KEY]
Win2000 returns the desired record/value shown above. Win2k3 does not.
HOWEVER, if on the Win2k3 box I modify the script to become "5.2M*" it
then works. Is the period (.) affecting this as a word breaker? Why
would the "M" have to be supplied to retrieve "5.2MM"? A user should
rightfully expect to get back "5.2MM" when they enter "5.2*".
Further examples between the two envrionments:
"5.2*" - (Win2k3 - Doesn't work) | (Win2000 - Does work)
'5.2M*" - (Win2k3 - Does work) | (Win2000 - Does work)
"5.2MM" - (Win2k3 - Does work) | (Win2000 - Does work)
"5*2MM" - (Win2k3 - Does work) | (Win2000 - Doesn't work)
"5 2MM" - (Win2k3 - Does work) | (Win2000 - Doesn't work)
"2MM" - (Win2k3 - Does work) | (Win2000 - Doesn't work)
Again, the first example (5.2*) is the one I'm concerned about because
a user should expect to get back the result. Also, if the word
breaker is the issue, I do not want to use the neutral word breaker
because we need to use the inflectional search option.
Thanks for any help.
Tim
Did you make any changes to the ignored words lists on either server?
Also, 5*2MM is not going to produce any useful results because it's not
supported. You getting the expected result on Windows 2003 is mere
coincidence.
--
Dan
- Follow-Ups:
- Re: SQL 2000 FTS - Different results between Win2k3 and Win2000
- From: Daniel Crichton
- Re: SQL 2000 FTS - Different results between Win2k3 and Win2000
- References:
- SQL 2000 FTS - Different results between Win2k3 and Win2000
- From: Tim F
- Re: SQL 2000 FTS - Different results between Win2k3 and Win2000
- From: Daniel Crichton
- SQL 2000 FTS - Different results between Win2k3 and Win2000
- Prev by Date: Re: SQL 2000 FTS - Different results between Win2k3 and Win2000
- Next by Date: Re: Error Msg 30053 - Word breaking timed out for the full-text query string
- Previous by thread: Re: SQL 2000 FTS - Different results between Win2k3 and Win2000
- Next by thread: Re: SQL 2000 FTS - Different results between Win2k3 and Win2000
- Index(es):
Relevant Pages
|
