accent sensitive

Hello
just a little question :
in full text search, in SQL Server 2000, how to enable accent-insentive?
for exemple : if I seize "tele", I want to have results with "tl", "tele",
"tle" and "tel"
thanks for your answer!
a+
syl
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
"lobrys" <REMOVE_MElobrys@.orange.com> wrote in message
news:uJKhJpmdFHA.2776@.TK2MSFTNGP10.phx.gbl...
> Hello
> just a little question :
> in full text search, in SQL Server 2000, how to enable accent-insentive?
> for exemple : if I seize "tele", I want to have results with "tl",
"tele",
> "tle" and "tel"
> thanks for your answer!
> a+
> syl
>

Accent problem

I'm having a problem with character accentuation in SQL Server 2000.
The database was created with SQL_Latin1_General_CP850_CI_AI Collation and
table varchar fields are using the same collation.
The problem happens when I use characters with accentuation, database is not
saving the correct character value, I don't know if it is a client
configuration problem or a database configuration problem.
If I insert the character 'á', it is saving as '?'.
I think it is not a collate problem because I'm trying to select the field
using a different collate but the character still wrong.
select my_field collate SQL_Latin1_General_CP1_CS_AS
from my_table
I don't how to solve this problem, it's a collation problem? Client
configuration problem?
Some help will be usefull.
Thanks.
Its hard to say. There are some problems with some of the input mechanisms.
For instance if you input text files into a text or varchar column using the
ado stream object, they seem to go in as Unicode with an unknown code page.
Converting the text files to ANSI and then importing them seems to fix this
behavior.
It could also be related to the regional settings on the client computer.
Exactly how are you inputting these characters.
"Depaula" <Depaula@.discussions.microsoft.com> wrote in message
news:172EDC2E-1BEF-496A-AB27-529B0C1EF4D9@.microsoft.com...
> I'm having a problem with character accentuation in SQL Server 2000.
> The database was created with SQL_Latin1_General_CP850_CI_AI Collation and
> table varchar fields are using the same collation.
> The problem happens when I use characters with accentuation, database is
> not
> saving the correct character value, I don't know if it is a client
> configuration problem or a database configuration problem.
> If I insert the character 'á', it is saving as '?'.
> I think it is not a collate problem because I'm trying to select the field
> using a different collate but the character still wrong.
> select my_field collate SQL_Latin1_General_CP1_CS_AS
> from my_table
> I don't how to solve this problem, it's a collation problem? Client
> configuration problem?
> Some help will be usefull.
> Thanks.
|||I have an application that inserts data collected from users, it is very
curious because I have the same applications working in other databases and
it works right.
Only in this situation I have this problem and I don't know how to identify
where is the problem.
In first time I thought that problem was the database collation, but when I
select data using other collation the problem still happening.
** The text fields are varchar(254).
Thanks for help me.
"Hilary Cotter" wrote:

> Its hard to say. There are some problems with some of the input mechanisms.
> For instance if you input text files into a text or varchar column using the
> ado stream object, they seem to go in as Unicode with an unknown code page.
> Converting the text files to ANSI and then importing them seems to fix this
> behavior.
> It could also be related to the regional settings on the client computer.
> Exactly how are you inputting these characters.
>
> "Depaula" <Depaula@.discussions.microsoft.com> wrote in message
> news:172EDC2E-1BEF-496A-AB27-529B0C1EF4D9@.microsoft.com...
>
>
|||are the regional settings of both machines identical?
"Depaula" <Depaula@.discussions.microsoft.com> wrote in message
news:9615ED1B-EF46-4F3D-B491-BC9703A029D8@.microsoft.com...
> I have an application that inserts data collected from users, it is very
> curious because I have the same applications working in other databases
and
> it works right.
> Only in this situation I have this problem and I don't know how to
identify
> where is the problem.
> In first time I thought that problem was the database collation, but when
I[vbcol=seagreen]
> select data using other collation the problem still happening.
> ** The text fields are varchar(254).
> Thanks for help me.
>
> "Hilary Cotter" wrote:
mechanisms.[vbcol=seagreen]
the[vbcol=seagreen]
page.[vbcol=seagreen]
this[vbcol=seagreen]
computer.[vbcol=seagreen]
and[vbcol=seagreen]
is[vbcol=seagreen]
field[vbcol=seagreen]
|||Have you tested to define your column as unicode column : nvarchar and not
varchar ?
Phil.
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:e50MWXisEHA.3572@.tk2msftngp13.phx.gbl...[vbcol=seagreen]
> are the regional settings of both machines identical?
> "Depaula" <Depaula@.discussions.microsoft.com> wrote in message
> news:9615ED1B-EF46-4F3D-B491-BC9703A029D8@.microsoft.com...
> and
> identify
when[vbcol=seagreen]
> I
> mechanisms.
using[vbcol=seagreen]
> the
> page.
> this
> computer.
Collation[vbcol=seagreen]
> and
database
> is
> field
>
|||Hi Philippe,
Hmm... You are correct as Depaula's first posting indicated that he was
using "...and table varchar fields are using the same collation" and not
nvarchar!
Regards,
John
"Philippe [MS]" <ptrotin@.online.microsoft.com> wrote in message
news:u9$oczWtEHA.1220@.TK2MSFTNGP10.phx.gbl...[vbcol=seagreen]
> Have you tested to define your column as unicode column : nvarchar and not
> varchar ?
> Phil.
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:e50MWXisEHA.3572@.tk2msftngp13.phx.gbl...
very[vbcol=seagreen]
databases[vbcol=seagreen]
> when
> using
code[vbcol=seagreen]
fix[vbcol=seagreen]
2000.[vbcol=seagreen]
> Collation
> database
the[vbcol=seagreen]
Client
>

accent insensitive search and SPS

What about this?
http://www.cfgigolo.com/unsorted/fts..._sensitive.txt
I don't need to run SPS and SQL 2K on the same machine so it would be no
problem to overwrite MSSearch
Is it safe to do it?
Thanks
Matias
The binaries for the version of MSSearch which ships Sharepoint 2003 are
radically different from the ones which ship with SQL 2000 FTS. I would not
advise you to do this.
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
"Matias Woloski" <woloski@.NOSPAMsion.com> wrote in message
news:u%235VxECVFHA.3760@.TK2MSFTNGP15.phx.gbl...
> What about this?
> http://www.cfgigolo.com/unsorted/fts..._sensitive.txt
> I don't need to run SPS and SQL 2K on the same machine so it would be no
> problem to overwrite MSSearch
> Is it safe to do it?
> Thanks
> Matias
>

accent insensitive full text search

I am running SQL 2000 SP3a on Windows 2000.
Is it possible to obtain accent insensitive results from full-text searches
so that a search for caf will return all records for caf and cafe as if
these were the same?
In the four queries below queries 2a and 2b return the same results as each
other whereas queries 1a and 1b return different results from each other.
1a. select * from MyTable where CONTAINS(*,'cafe')
1b. select * from MyTable where CONTAINS(*,'caf')
2a. select * from MyTable where searchtext like '%cafe%'
2b. select * from Mytable where searchtext like '%caf%'
Thanks
Joseph
No,it is not possible.
This issue has already been discussed in detail several times, do a search
in this newsgroup.
Matthias
"Joseph Tervit" <joseph@.company-net.com> wrote in message
news:eaRfNYeMEHA.1340@.TK2MSFTNGP12.phx.gbl...
> I am running SQL 2000 SP3a on Windows 2000.
> Is it possible to obtain accent insensitive results from full-text
searches
> so that a search for caf will return all records for caf and cafe as if
> these were the same?
> In the four queries below queries 2a and 2b return the same results as
each
> other whereas queries 1a and 1b return different results from each other.
> 1a. select * from MyTable where CONTAINS(*,'cafe')
> 1b. select * from MyTable where CONTAINS(*,'caf')
> 2a. select * from MyTable where searchtext like '%cafe%'
> 2b. select * from Mytable where searchtext like '%caf%'
> Thanks
> Joseph
>
|||Joseph,
Matthias, yes this has been discussed many, many (too many) times in this
newsgroup, IMHO. However, with the new Microsoft newsgroup msg roll-off
policy, the past replies might not be searchable (except via Google groups,
of course! ;-). One easy solution is to simply install SharePoint Server
2001 or 2003 as either will upgrade the MSSearch service to the SPPS version
that does support accent insensitive search.
Regards,
John
"Matthias HALDIMANN" <matthias.haldimann@.epfl.ch> wrote in message
news:409883a9$1@.epflnews.epfl.ch...[vbcol=seagreen]
> No,it is not possible.
> This issue has already been discussed in detail several times, do a search
> in this newsgroup.
> Matthias
>
> "Joseph Tervit" <joseph@.company-net.com> wrote in message
> news:eaRfNYeMEHA.1340@.TK2MSFTNGP12.phx.gbl...
> searches
if[vbcol=seagreen]
> each
other.
>
|||Hi,
I have two questions relating to your suggestion of installing sharepoint.
1. will this work for both sql fts and indexing server fts
(I currently have a file system catolog that I have linked into slq server, I do joined queries that search that catalog and and sql catalog for the same phrases)
2. if so, hwo do I rebuild the catalogs to be case insensitive?
thanks in advance
randyr
"John Kane" wrote:

> Joseph,
> Matthias, yes this has been discussed many, many (too many) times in this
> newsgroup, IMHO. However, with the new Microsoft newsgroup msg roll-off
> policy, the past replies might not be searchable (except via Google groups,
> of course! ;-). One easy solution is to simply install SharePoint Server
> 2001 or 2003 as either will upgrade the MSSearch service to the SPPS version
> that does support accent insensitive search.
> Regards,
> John
>
>
> "Matthias HALDIMANN" <matthias.haldimann@.epfl.ch> wrote in message
> news:409883a9$1@.epflnews.epfl.ch...
> if
> other.
>
>
|||Randyr,
Hmm... a blast from the past... a past posting of mine...
1. will this work for both sql fts and indexing server fts
A. No. While the SQL FTS and Indexing Services use the same basic underlying
technology, they are implemented differently and SharePoint was developed
after both of these products were shipped.
2. if so, how do I rebuild the catalogs to be case insensitive?
A. You cannot rebuild a SQL Server 2000 FT Catalog to be "case insensitive"
or "accent insensitive" as I'm assuming that's what you meant to say...
.. However, this will be possible with SQL Server 2005 (Yukon) this will be
supported via T-SQL: "CREATE FULLTEXT CATALOG FT_Catalog_Name WITH
ACCENT_SENSITIVITY = OFF AS DEFAULT"
Either way, I'd highly recommend that you test this functionality this in a
test environment FIRST before implementing it on your production servers.
Regards,
John
"randyr" <randyr@.online.nospam> wrote in message
news:70BBE3FA-EA50-4D76-9E45-F52B3E5812CF@.microsoft.com...
> Hi,
> I have two questions relating to your suggestion of installing sharepoint.
> 1. will this work for both sql fts and indexing server fts
> (I currently have a file system catolog that I have linked into slq
server, I do joined queries that search that catalog and and sql catalog for
the same phrases)[vbcol=seagreen]
> 2. if so, hwo do I rebuild the catalogs to be case insensitive?
> thanks in advance
> --
> randyr
>
> "John Kane" wrote:
this[vbcol=seagreen]
groups,[vbcol=seagreen]
version[vbcol=seagreen]
search[vbcol=seagreen]
as[vbcol=seagreen]
as[vbcol=seagreen]