Full Text Index for international Addresses

Hello

I am working on a database with a address table and a subtable addresslines
containing all address data like street, name zip and so on...as it is
international I have german address notation like Diesestrasse and English
like Blvd and so on. I store the country in the address table (CountryId) and
so I would like to build a full text index with the LCID from this table (not
xml). Is there a way to do so?

The next question is how to manage this whole thing with the subset of
addresslines so I can search for them in one index (maybe with an indexed
view?)...I would create another table I manage with triggers...maybe someone
has a better idea (I do not really like the indexed views).

There are ways of doing this where you tag your content with language tags
which ifilters can understand and then break the words according to the
language rules for that language.

For example you could store the documents in Word, XML, or HTML and use the
language tags to mark the language of the addresses.

This way Diesestraße will be indexed and searchable as Diesestraße and
diese (assuming it is removed from the noise word list), and straße.

Then if you apply the language parameter in your searches you will maximize
the correct number of hits being returned and minimize the program with
false friends/conjugates.

Now you also should really include a column with your language and then
restrict only hits coming back from the language you are searching on/in.

"nietZsche" wrote in message

> Hello
>
> I am working on a database with a address table and a subtable
> addresslines
> containing all address data like street, name zip and so on...as it is
> international I have german address notation like Diesestrasse and English
> like Blvd and so on. I store the country in the address table (CountryId)
> and
> so I would like to build a full text index with the LCID from this table
> (not
> xml). Is there a way to do so?
>
> The next question is how to manage this whole thing with the subset of
> addresslines so I can search for them in one index (maybe with an indexed
> view?)...I would create another table I manage with triggers...maybe
> someone
> has a better idea (I do not really like the indexed views).