Multilingual Full-Text support

Multilingual Full-Text support

Post by Armin Kastne » Sun, 06 Aug 2000 04:00:00



We have a requirement to provide full-text search on both English and French
text in the same database.The text data is in different columns and
different catalogs have been created. However, when creating the indexes,
only the SQL Server installed language is used, resulting in only a single
set of noise words being applied, in this case English. Therefore, the same
noise words are applied for both English and French indexes, which creates a
problem if someone wants to search for 'The'  (tea) in French for example.

I just wondered if anyone else has run across a similar problem and if
anyone has resolved it. I'm wondering if this is a serious limitation in the
full-text search support provided by Microsoft.

One solution is to replicate the database to another server that has been
installed using French and then doing the French text searches on that
server. This is probably too complex and costly for our client.

If you can help or have any comments, please send e-mail direct to

 
 
 

Multilingual Full-Text support

Post by Paul » Wed, 09 Aug 2000 04:00:00


SQL 2000 allows you to set different 'collations' (how they are called now)
on different columns of the same table.

> We have a requirement to provide full-text search on both English and
French
> text in the same database.The text data is in different columns and
> different catalogs have been created. However, when creating the indexes,
> only the SQL Server installed language is used, resulting in only a single
> set of noise words being applied, in this case English. Therefore, the
same
> noise words are applied for both English and French indexes, which creates
a
> problem if someone wants to search for 'The'  (tea) in French for example.

> I just wondered if anyone else has run across a similar problem and if
> anyone has resolved it. I'm wondering if this is a serious limitation in
the
> full-text search support provided by Microsoft.

> One solution is to replicate the database to another server that has been
> installed using French and then doing the French text searches on that
> server. This is probably too complex and costly for our client.

> If you can help or have any comments, please send e-mail direct to



 
 
 

1. Multilingual full-text search support

We have a requirement to provide full-text search on both English and French
text in the same database.The text data is in different columns and
different catalogs have been created. However, when creating the indexes,
only the SQL Server installed language is used, resulting in only a single
set of noise words being applied, in this case English. Therefore, the same
noise words are applied for both English and French indexes, which creates a
problem if someone wants to search for 'The'  (tea) in French for example.

I just wondered if anyone else has run across a similar problem and if
anyone has resolved it. I'm wondering if this is a serious limitation in the
full-text search support provided by Microsoft.

One solution is to replicate the database to another server that has been
installed using French and then doing the French text searches on that
server. This is probably too complex and costly for our client.

If you can help or have any comments, please send e-mail direct to

2. Connecting from VB3.0 to Access2.0 via ODBC

3. multilingual full-text-search

4. Access key in menu bar in Visual basic

5. Scheduled full-text incremental population for full-text catalog

6. Crosstab pivot table sample code?

7. Year 2000 problems in MS-Access when using MULTINATIONAL date format.

8. Full - text Indexing support

9. cannot see full text in support services

10. Full-text support information?

11. Full-text search language support

12. Full Text support in SQL Server 2000