Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
gmerideth
Starting Member
10 Posts |
Posted - 2004-09-08 : 22:50:13
|
| I've got a table with a 'coderesponse' column which is a text field (under sql2k) and its set to be indexed by the full text engine. The unique id is a numeric set to be an identity field called 'codeID'.I've put in ~100 records all with valid data I'm looking to get back however it fails on even simple queries.When I do:SELECT FT_TBL.codeID, FT_TBL.Subject, KEY_TBL.RANKFROM ftCodeLibrary AS FT_TBL INNER JOINCONTAINSTABLE (ftCodeLibrary, coderesponse, '("using")') AS KEY_TBLON FT_TBL.codeID = KEY_TBL.[KEY] ORDER BY KEY_TBL.RANK DESCI get back a result set of ~22 files (which is right) and their relative ranking. However..if I query:...CONTAINSTABLE (ftCodeLibrary, coderesponse, '("System")') AS KEY_TBL...I get back zero results. none..nada...zilch.The 'coderesponse' for *all* 22 records has "using System;" as their first line, why does 'using' get 22 but 'System' gets none? I can find things like 'Console' from a line of "Console.Writeline" but not 'Writeline" /boggle.I've tried ('System') and ('"System"') and I get back nada.What am I doing wrong here? |
|
|
AndrewMurphy
Master Smack Fu Yak Hacker
2916 Posts |
Posted - 2004-09-09 : 07:52:32
|
| are you hitting "noise" words...ie words that FTI is programmed to ignore....like "the", "and", "is"...etc? |
 |
|
|
gmerideth
Starting Member
10 Posts |
Posted - 2004-09-09 : 10:48:37
|
| I dont think so. The query for "using" produces (now) 30 results all of which contain the word "using" in the body of the text. The quer for "System" returns 0 results even though the sql text is "using System;" as the first line of the body. Is is the ";" thats causing it? Do I need to use a 'near' or something? A line in the body of the record is "Console.Writeline" is found with "Console" but not "Writeline". I think its the "."'s but that just seems pretty bad if SQL ignores the query due to a ".". |
 |
|
|
|
|
|