SQLServerCentral / Discuss Content Posted by Chris Kempster / Article Discussions / Article Discussions by Author / Full Text Indexing - Text Parsing Routine / Latest Posts

RE: Full Text Indexing - Text Parsing Routine

trullock — Wed, 06 Aug 2008 10:33:41 GMT

Hi, I really liked this code :)I've ported it into C# to give me more control over the search term, I'd love to know what you guys think :)Check it out: [url=http://www.muonlab.com/uncategorized/how-to-build-an-sql-full-text-index-search-term-in-c/]How to build an SQL full text index search term in c#[/url]Trull[url=http://www.muonlab.com]muonlab web development blog[/url]

RE: Full Text Indexing - Text Parsing Routine

ckempste — Thu, 18 Dec 2003 00:40:00 GMT

hi there, very observant actually, this is a bug, we altered it just the other day to 2000, the size really blows out for large search strings... thanks again.Chris Kempsterwww.chriskempster.comAuthor of "SQL Server 2k for the Oracle DBA"

RE: Full Text Indexing - Text Parsing Routine

ojm@webf1.com — Wed, 17 Dec 2003 23:49:00 GMT

Very much appreciated. I've not yet done a lot of testing or looked at the logic in detail, however, I did notice something peculiar. If the input parameter is varchar(500), how can the output parameter also be varchar(500)? If I indeed send all 500 characters in, it seems the result coming back would be truncated.This is just a minor detail, but it could create problem that could be hard to diagnose.

RE: Full Text Indexing - Text Parsing Routine

ckempste — Thu, 11 Dec 2003 07:03:00 GMT

With the é (accented characters). No matter the language settings for the character fields (ie. accent insensitive), we found the é and other such characters wouldnt translate, so café wouldnt come up if we searched for cafe for example, this was a real pain to deal with, therefore stripping was required. If someone has a solution for this, id love to hear it.CheersCkChris Kempsterwww.chriskempster.comAuthor of "SQL Server 2k for the Oracle DBA"

RE: Full Text Indexing - Text Parsing Routine

ckempste — Thu, 11 Dec 2003 03:24:00 GMT

For those interested, alter the final @search assignment to this:SELECT @search = 'ISABOUT("' + @rawsearch + '" WEIGHT(.8), ' + @search2 + ' WEIGHT (.7), ' + @search + ' WEIGHT(.6)) OR (' + @fuzzy + ')'and it will change it to this:ISABOUT("drive safe" WEIGHT(.8), "drive" near "safe" WEIGHT (.7), "drive*" near "safe*" WEIGHT(.6)) OR (FORMSOF(INFLECTIONAL,"drive") AND FORMSOF(INFLECTIONAL,"safe"))Note that: FORMSOF(INFLECTIONAL,"drive","safe")does an OR, which cant be used in the above statement, only AND between formsof statements.CheersCkChris Kempsterwww.chriskempster.comAuthor of "SQL Server 2k for the Oracle DBA"

RE: Full Text Indexing - Text Parsing Routine

ckempste — Thu, 11 Dec 2003 02:03:00 GMT

Hi thereVery nice indeed, I will alter the routine with a new parameter for this option and see how it goes in test.Thanks again.CheersCkChris Kempsterwww.chriskempster.comAuthor of "SQL Server 2k for the Oracle DBA"

RE: Full Text Indexing - Text Parsing Routine

Razvan Socol — Thu, 11 Dec 2003 00:43:00 GMT

1. How about the following condition:ISABOUT("drive safe" WEIGHT (.8), "drive" NEAR "safe" WEIGHT (.7), "drive*" NEAR "safe*" WEIGHT (.6), FORMSOF(INFLECTIONAL,"drive","safe") .5)Would it be better ?2. What is the idea with "é type characters" ?RazvanEdited by - rsocol on 12/11/2003 12:57:56 AM

Full Text Indexing - Text Parsing Routine

ckempste — Fri, 28 Nov 2003 00:00:00 GMT

Comments posted to this topic are about the content posted at http://www.sqlservercentral.com/columnists/ckempster/fulltextindexingtextparsingroutine.asp