unmatched result

unmatched result

Post by James La » Sat, 15 Jan 2005 13:50:16


Hi,

I have 2 database with same data and structure running on 2 different
machine on sql2000 sp3. However, the full-text search come out with
different result set. Any idea to fix the problem.

Thank you in advance for all your help.

James
 
 
 

unmatched result

Post by John Kan » Sat, 15 Jan 2005 15:05:26

James,
Yes. Could you post the full output of the following SQL script from both
machines and if possible as an attached .txt or .rpt file?

use <your_database_name_here>
go
SELECT @@language
SELECT @@version
-- may need to set advance options..
EXEC sp_configure 'default full-text language'
EXEC sp_help_fulltext_catalogs
EXEC sp_help_fulltext_tables
EXEC sp_help_fulltext_columns
EXEC sp_help <your_FT-enable_table_name_here>
go

Also, can you confirm that you have run a recent Full Population on both
servers as well as confirm that the language-specific noise word file
(noise.enu = US_English) content under the \FTDATA\SQLServer\Config is
exactly the same on both servers. Finally, if this is a clustered
environment, have the server's failed over recently? Specifically, see KB
article: 889708 "The full-text search results that are returned in a
clustered SQL Server 2000 environment may be different when the active node
changes" at http://www.yqcomputer.com/ ;en-us;889708
for additional information.

Finally, could you provide the exact CONTAINS or FREETEXT query you are
using as well as sample data from both servers?

Thanks,
John
--
SQL Full Text Search Blog
http://www.yqcomputer.com/

 
 
 

unmatched result

Post by Hilary Cot » Sat, 15 Jan 2005 21:18:48

What do you mean by different results sets? Is the number or rows returned
different or is the order different? Are these machines running the same OS?

Also is the regional settings the same on both machines?

--
Hilary Cotter
Looking for a SQL Server replication book?
http://www.yqcomputer.com/
 
 
 

unmatched result

Post by John Kan » Sat, 15 Jan 2005 23:51:14

You're welcome, James,
First of all, thank you for providing the requested information as the
@@version info is the key to understanding why the FTS results for the same
SQL FTS query, with the same noise word file (noise.enu = US_English = 1033,
in this case) is different:

-- From: wosvr15.rpt
SQL Server 2000 - 8.00.760
Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 1, v.1023)
default full-text language: 1033
FT Catalog name: odmProductCat at C:\MSSQL\FTDATA
FT Table name: ecProductInfo with 5 columns FT-enabled and all using
FULLTEXT_LANGUAGE: 1033

-- From: wosvr03.rpt
SQL Server 2000 - 8.00.760
Enterprise Edition on Windows NT 5.0 (Build 2195: Service Pack 3)
default full-text language: 1033
FT Catalog name: odmProductCat at d:\MSSQL\FTDATA
FT Table name: ecProductInfo with 5 columns FT-enabled and all using
FULLTEXT_LANGUAGE: 1033


Note, that you have two different OS platforms: wosvr15 is using Windows
Server 2003 (Win2003) and wosvr03 is using Windows 2000 Server (Win2K) and
these two OS Platforms supply the OS-specific wordbreaker dll. See my many
posts on this via http://www.yqcomputer.com/ +infosoft as
this and the fact that some of your actual data may have punctuation
characters in contact (touching) the search words and this could explain the
different results.

Hope that helps!
John
--
SQL Full Text Search Blog
http://www.yqcomputer.com/





node