Showing posts with label indexing. Show all posts
Showing posts with label indexing. Show all posts

Friday, March 9, 2012

French characters on English Platform dropped

Hi all,
I Had installed an english platform with full text indexing enable.
My data are French (with some accents for example).
When I search with a CONTAINS Statement on my Data, SQL Server drops my
accentuates characters.
How can I resolve this problem ?
What must I install on my platform to resolve this problem ?
Thanks for your answers.
Alex.
Exactly what do you mean by this.
Do you mean that a search on cafe will not match with a search on the
accented version of cafe?
This problem is fixed in SQL 2005.
In the meantime you have to expand your search on both the accented and
unaccented version of the search term.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Alexandre BARBIER" <(del_this)abarbier@.sopragroup.com> wrote in message
news:e8S11xylEHA.704@.TK2MSFTNGP09.phx.gbl...
> Hi all,
> I Had installed an english platform with full text indexing enable.
> My data are French (with some accents for example).
> When I search with a CONTAINS Statement on my Data, SQL Server drops my
> accentuates characters.
> How can I resolve this problem ?
> What must I install on my platform to resolve this problem ?
> Thanks for your answers.
> Alex.
>
|||Hi,
No, I mean that my data are in french version and my full text search turn
on an English Platform.
When I search a french word, the fulltext search dropped my accented
characters so my search doesn't work.
Any Ideas ?
Thanks.
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:%23CSrWe0lEHA.3016@.tk2msftngp13.phx.gbl...
> Exactly what do you mean by this.
> Do you mean that a search on cafe will not match with a search on the
> accented version of cafe?
> This problem is fixed in SQL 2005.
> In the meantime you have to expand your search on both the accented and
> unaccented version of the search term.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> "Alexandre BARBIER" <(del_this)abarbier@.sopragroup.com> wrote in message
> news:e8S11xylEHA.704@.TK2MSFTNGP09.phx.gbl...
>
|||Alexandre,
This has been a long outstanding bug in SQL Server 7.0 and SQL Server 2000,
that is only "fixed" in SQL Server 2005 (Yukon) via the following new T-SQL
syntax:
CREATE FULLTEXT CATALOG Employee_FTC WITH ACCENT_SENSITIVITY = ON
CREATE FULLTEXT CATALOG Employee_FTC WITH ACCENT_SENSITIVITY=OFF
-- Or by using ALTER FULLTEXT CATALOG:
ALTER FULLTEXT CATALOG Employee_FTC REBUILD WITH ACCENT_SENSITIVITY=ON
The SQL Server 7.0 or SQL Server 2000 solution requires the duplication of
the accented data with the removal of accents via a UDF and insert/update
trigger to maintain the duplicate data. You would create a FT Index on the
non-accented data and return the accented data to your searcher.
Regards,
John
"Alexandre BARBIER" <(del_this)abarbier@.sopragroup.com> wrote in message
news:eE9gBIWmEHA.412@.TK2MSFTNGP10.phx.gbl...[vbcol=seagreen]
> Hi,
> No, I mean that my data are in french version and my full text search turn
> on an English Platform.
> When I search a french word, the fulltext search dropped my accented
> characters so my search doesn't work.
> Any Ideas ?
> Thanks.
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:%23CSrWe0lEHA.3016@.tk2msftngp13.phx.gbl...
my
>

Friday, February 24, 2012

Free - Text Indexing

I am looking at a problem about intense CPU processing during a Background
Free Text reindexing. This happens about every 5 minutes (scheduled).
The key problem, is we are looking at putting the free text element onto
another hard disk controller to minimise. Would putting the Free-Text onto
another hard disk controller be sufficient or does it need to be associated
with another CPU.
This is on SQL 2000 Enterprise
Any advice would be helpful
Jack Vamvas
___________________________________
Advertise your IT vacancies for free at - http://www.ITjobfeed.comJack,
What does your disk I/O look like? Is it higher that it should be? If not,
then adding another disk and controller probably won't solve your problem
(although it is a good idea anyway to isolate full text catalogs). If CPU is
your bottleneck and there are no other influencing issues such as bad
indexes, etc., then adding another server exclusively for full text indexing
is probably the solution.
Full text catalogs are notoriously resource intensive on SQL 2K. Supposely,
SQL 2005 has improved the performance significantly, but I haven't verified
it myself. Maybe upgrading to 2005 should be in the plan as well.
-- Bill
"Tom" <DEL_TO_REPLY@.del.com> wrote in message
news:Z7OdnXKLyrVGPJvbnZ2dnUVZ8sOonZ2d@.bt
.com...
>I am looking at a problem about intense CPU processing during a Background
>Free Text reindexing. This happens about every 5 minutes (scheduled).
> The key problem, is we are looking at putting the free text element onto
> another hard disk controller to minimise. Would putting the Free-Text onto
> another hard disk controller be sufficient or does it need to be
> associated with another CPU.
> This is on SQL 2000 Enterprise
> Any advice would be helpful
> --
> Jack Vamvas
> ___________________________________
> Advertise your IT vacancies for free at - http://www.ITjobfeed.com
>
>

Free - Text Indexing

I am looking at a problem about intense CPU processing during a Background
Free Text reindexing. This happens about every 5 minutes (scheduled).
The key problem, is we are looking at putting the free text element onto
another hard disk controller to minimise. Would putting the Free-Text onto
another hard disk controller be sufficient or does it need to be associated
with another CPU.
This is on SQL 2000 Enterprise
Any advice would be helpful
--
Jack Vamvas
___________________________________
Advertise your IT vacancies for free at - http://www.ITjobfeed.comJack,
What does your disk I/O look like? Is it higher that it should be? If not,
then adding another disk and controller probably won't solve your problem
(although it is a good idea anyway to isolate full text catalogs). If CPU is
your bottleneck and there are no other influencing issues such as bad
indexes, etc., then adding another server exclusively for full text indexing
is probably the solution.
Full text catalogs are notoriously resource intensive on SQL 2K. Supposely,
SQL 2005 has improved the performance significantly, but I haven't verified
it myself. Maybe upgrading to 2005 should be in the plan as well.
-- Bill
"Tom" <DEL_TO_REPLY@.del.com> wrote in message
news:Z7OdnXKLyrVGPJvbnZ2dnUVZ8sOonZ2d@.bt.com...
>I am looking at a problem about intense CPU processing during a Background
>Free Text reindexing. This happens about every 5 minutes (scheduled).
> The key problem, is we are looking at putting the free text element onto
> another hard disk controller to minimise. Would putting the Free-Text onto
> another hard disk controller be sufficient or does it need to be
> associated with another CPU.
> This is on SQL 2000 Enterprise
> Any advice would be helpful
> --
> Jack Vamvas
> ___________________________________
> Advertise your IT vacancies for free at - http://www.ITjobfeed.com
>
>