April 29, 2008 at 6:34 am
hi:)
i am working with sql server express edition,in this i am creating full txt index on one particular column ,that column is resume image means its a document.
i want to search for skills in resume what ever i give ,but here is the problem occurred
when i give spl symbols mens like vc++,c# its not working ,its not giving any result.but when i give like .net,asp. this it will works fine.i dont know whats the problem.
plz any one help me out in this.
thanks in advance.
May 21, 2008 at 1:59 am
Read up on noise words and noise files in Books Online. You can remove individual noise words from the noise file for the appropriate language (or remove all words, and only keep a single space as the entire contents of the nopise file), and then rebuild the full-text index.
But consult Books Online *before* you attempt anything.
ML
---
Matija Lah, SQL Server MVP
http://milambda.blogspot.com
May 22, 2008 at 3:37 am
There is woefully little documentation about how SQL Full Text indexing works from Microsoft. You need to do a lot of Googling to find posts and documents that explain more.
There are a few FTS experts that have a number of useful posts - Hilary Cotter is one that comes to mind. Feel free to post your problems here, but please read Books Online first to get a basic understanding about how FTS works or you will spend a lot of time making basic mistakes.
Hopefully, there will be a lot more information from Microsoft with SQL Server 2008.
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
May 22, 2008 at 10:41 am
SQL Server's full-text CANNOT be used to search on punctuation characters ( , . - # ^ & ' " / + ? etc.). Additionally, single letters and single digits are, by default, considered "noise words". So you cannot search on "C++" or "C#" using full-text.
You can improve the situation a bit by removing words from the default, language specific, noise word list.
In summary, read up on full-text using the BOL or Hillary's very nice articles before implementing a full-text solution.
Done corectly, it works very well (constrained by the functionality limitations). You need to know and understand these limitations.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply