Hi Rob,
I've only been using it with up to a hundred entries but haven't noticed any huge speed hit. I presume in the case of an expansion, having 100 entries for the same thing would be like doing 1 query followed by 99 more on the cached data. Regards, Greg From: Rob von Nesselrode [mailto:[email protected]] Sent: Wednesday, 10 February 2010 6:57 PM To: [email protected]; 'ausDotNet' Subject: RE: SQL 2008 and thesaurus use THanks Greg, I'll have a read tonight. Any idea about any speed issues with FTS and the thesaurus? If I go that way I have to process about 200,000 records in daily (mostly repeats for now) and need maybe up to 1,000 entries in the thesaurus. The rest I can pick up with RHS truncation and judicious use of the LIKE keyword Fortunately its all in english R _____ From: [email protected] [mailto:[email protected]] On Behalf Of Greg Low (greglow.com) Sent: Wednesday, 10 February 2010 4:23 PM To: 'ausDotNet' Subject: RE: SQL 2008 and thesaurus use Would help if I'd included the link to the post: http://sqlblog.com/blogs/greg_low/archive/2008/08/13/modifying-the-thesaurus -in-full-text-search-in-sql-server-2008.aspx Regards, Greg From: [email protected] [mailto:[email protected]] On Behalf Of Greg Low (greglow.com) Sent: Wednesday, 10 February 2010 5:09 PM To: 'ausDotNet' Subject: RE: SQL 2008 and thesaurus use Hi Rob, I did a blog post here about where the files are that need to be modified (different to what books online says). A typical sample looks like this: <XML ID="Microsoft Search Thesaurus"> <!-- Commented out (SQL Server 2008) <thesaurus xmlns="x-schema:tsSchema.xml"> <diacritics_sensitive>0</diacritics_sensitive> <expansion> <sub>Internet Explorer</sub> <sub>IE</sub> <sub>IE5</sub> </expansion> <replacement> <pat>NT5</pat> <pat>W2K</pat> <sub>Windows 2000</sub> </replacement> <expansion> <sub>run</sub> <sub>jog</sub> </expansion> </thesaurus> --> <thesaurus xmlns="x-schema:tsSchema.xml"> <diacritics_sensitive>0</diacritics_sensitive> <expansion> <sub>user</sub> <sub>punter</sub> <sub>friend</sub> </expansion> </thesaurus> </XML> You can do expansions and replacements. There are two things I've seen issues with: 1. Don't create an infinite nesting in the expansions. 2. There's only one file per instance. It would be way better if it was per-database instead, particularly for anyone that needs to work in a hosted environment. If you have access to TechEd Online, I've got sessions up there using it. One's called "Answering the queries your users really want to ask". HTH, Greg <snip>
