Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
DB Engine
SQL ServerMSDESQL Server CE
Services
Analysis (Data Mining)Analysis (OLAP)DTSIntegration ServicesNotification ServicesReporting Services
Programming
CLRConnectivitySQLXML
Other Technologies
ClusteringEnglish QueryFull-Text SearchReplicationService Broker
General
Data WarehousingPerformanceSecuritySetupSQL Server ToolsOther SQL Server Topics
DirectoryUser Groups
Related Topics
MS AccessOther DB ProductsMS Server Products.NET DevelopmentVB DevelopmentJava DevelopmentMore Topics ...

SQL Server Forum / Other Technologies / Full-Text Search / October 2005

Tip: Looking for answers? Try searching our database.

Strange results

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Kirsten - 27 Oct 2005 00:42 GMT
I have a fulltext index on the "INSUMOS" table with the following options:

1) Default language is spanish
2) The NOISE.ESN is empty (i.e. index everything)
3) The catalog is updated

If I run the following query I don't get the expected results:

select Nombre from insumos
where CONTAINS(Insumos.Nombre, '"vase*"')

I get:

Valvula hidrocefalia presion baja
Vaselina solida pote Env x 200 grs
Otros varios
Varios
Especulo vaginal mediano 32-120-02

Why is this happening? Any ideas?
Thanks!
John Kane - 27 Oct 2005 03:46 GMT
Kirsten,
Could you post the full output of the following SQL code? This will help me
gather info on your environment and help provide more direct and faster
answers.

use <your_database_name_here>
go
SELECT @@language
SELECT @@version
-- will need to set 'show advance options' first...
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

Are the words or phrases that you expect are the accented words? For
example, cafe vs. Café (note, the accent on the e).
If so, you should bear in mind that SQL Server 2000 is not accent sensitive,
i.e.. accent in-sensitive and that this is fixed only in SQL Server 2005.

If not, do you get the expected results if you alter the CONTAINS query and
not reference the "tablename.columnname", for example:

select Nombre from insumos
where CONTAINS(Nombre, '"vase*"')

Thanks,
John
Signature

SQL Full Text Search Blog
http://spaces.msn.com/members/jtkane/

>I have a fulltext index on the "INSUMOS" table with the following options:
>
[quoted text clipped - 17 lines]
> Why is this happening? Any ideas?
> Thanks!
Hilary Cotter - 27 Oct 2005 11:53 GMT
Is this one or 4 rows? Vaselina is a match to the wildcarded vase.

Signature

Hilary Cotter
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

> I have a fulltext index on the "INSUMOS" table with the following options:
>
[quoted text clipped - 17 lines]
> Why is this happening? Any ideas?
> Thanks!
Kirsten - 27 Oct 2005 19:34 GMT
5 rows. And yes: "Vaselina" is supposed to match but not the others.
Thanks!

> Is this one or 4 rows? Vaselina is a match to the wildcarded vase.
>
[quoted text clipped - 19 lines]
> > Why is this happening? Any ideas?
> > Thanks!
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.