{"id":299,"date":"2014-10-16T09:30:50","date_gmt":"2014-10-16T08:30:50","guid":{"rendered":"http:\/\/www.codereview.co\/?p=299"},"modified":"2014-10-15T14:44:08","modified_gmt":"2014-10-15T13:44:08","slug":"sql-server-freetext-command-of-expanded-search","status":"publish","type":"post","link":"http:\/\/www.codereview.co\/index.php\/sql-server-tutorials\/sql-server-freetext-command-of-expanded-search\/","title":{"rendered":"SQL Server FREETEXT command of expanded search"},"content":{"rendered":"

Scenario<\/strong><\/span><\/p>\n

I have been reading about the Full Text Search capabilities in SQL Server 2005 and your tips have been a big help to improve how we query our data.\u00a0 Thus far converting our core queries to leverage Full Text Search has been a big help.\u00a0 I have been seeing information about the FREETEXT command and I would like to learn how to use this FREETEXT command versus the CONTAINS command.\u00a0 Should I use the FREETEXT command over the CONTAINS command or vice versa?\u00a0 Can you also provide some examples of using the FREETEXT command to learn about the variety of capabilities available?<\/span><\/p>\n

\u00a0<\/strong><\/span><\/p>\n

Solution<\/strong><\/span><\/p>\n

Yes – Let’s take a look at the comparison first and then we can work through a few different examples.\u00a0 The FREETEXT command is another alternative to access the data indexed by Full Text Search.\u00a0 In general the FREETEXT command provides the ability to search for a matched term based on the meaning of the terms as opposed to the exact character string.\u00a0 At a high level, this commands finds matches based on separating the string into individual words, determining inflectional versions of the word and using a thesaurus to expand or replace the term to improve the search.<\/span><\/p>\n

Now let’s compare the FREETEXT functionality with the CONTAINS command.\u00a0 The CONTAINS command uses exact match or fuzzy logic to perform the matches with a single word or a phrase.\u00a0 In addition, the words near another word can be found as well as performing a weighted match of multiple words where each word has a weight as compared to the others that are searched.\u00a0 Check out CONTAINS (Transact-SQL) for a explanation on the CONTAINS command.<\/span><\/p>\n

Depending on the search you are performing dictates which Full Text Search command you should use.\u00a0 Keep in mind that FREETEXT and CONTAINS are only two of the four commands available.\u00a0 The other two commands are CONTAINSTABLE and FREETEXTTABLE.\u00a0 The comparison between the four commands will be saved for a future tip since it is fairly involved explanation that should include examples.\u00a0<\/span><\/p>\n

Until that point in time, here is one data point to consider: according to SQL Server 2005 Books Online FREETEXT (Transact-SQL) “Full-text queries using FREETEXT are less precise than those full-text queries using CONTAINS. The SQL Server full-text search engine identifies important words and phrases. No special meaning is given to any of the reserved keywords or wildcard characters that typically have meaning when specified in the <contains_search_condition> parameter of the CONTAINS predicate.”\u00a0 Based on my testing, when the basic terms are queried with either command similar results are returned, so the precise factor for simple queries seems less of an issue.\u00a0 For complex searches the CONTAINS command wins hands down with the ability to use wild cards, NEAR statements, etc. As such, if the flexibility of the search is built into the front end application then the highest level of flexibility on the back end, between the FREETEXT and CONTAINS commands, tips the scales toward the CONTAINS command.<\/span><\/p>\n

FREETEXT Examples <\/em><\/strong><\/span><\/p>\n

Let’s take a look at the command reference and a few FREETEXT examples to use as a point of reference and comparison with the other Full Text Search.<\/span><\/p>\n\n\n\n\n\n\n\n\n\n\n
FREETEXT Command Syntax<\/strong><\/span><\/td>\n<\/tr>\n
FREETEXT ( { column_name | (column_list) | * } , ‘freetext_string’ [ , LANGUAGE language_term ] )<\/span>Source – SQL Server 2005 Books Online (FREETEXT (Transact-SQL))<\/em><\/span><\/td>\n<\/tr>\n
Simple FREETEXT Command<\/strong><\/span><\/td>\n<\/tr>\n
USE AdventureWorks; GO SELECT * FROM Production.Product WHERE FREETEXT(*, ‘nut screw washer’); GO \u00a0<\/span><\/td>\n<\/tr>\n
Literal Search with the FREETEXT Command<\/strong><\/span><\/td>\n<\/tr>\n
USE AdventureWorks; GO SELECT * FROM Production.Product WHERE FREETEXT(*, ‘”flat washer”‘); GO \u00a0<\/span><\/td>\n<\/tr>\n
FREETEXT Command with Input Parameters<\/strong><\/span><\/td>\n<\/tr>\n
USE AdventureWorks; GO DECLARE @SearchWord nvarchar(30); SET @SearchWord = N’nut screw washer’; SELECT * FROM Production.Product WHERE FREETEXT(*, @SearchWord); GO<\/span>*** NOTE *** – As a point of reference, use an nvarchar data type to prevent an implicit conversion.<\/em><\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
\u00a0<\/span><\/p>\n
Thanks for reading this article,<\/strong><\/span><\/p>\n
Next steps :<\/strong><\/span><\/p>\n
\n
Add this article to your database toolkit<\/strong><\/b><\/span><\/li>\n
Share this with your colleagues because Sharing is Learning<\/strong><\/span><\/li>\n
Comment below if you need any assistance<\/strong><\/span><\/li>\n<\/ol>\n","protected":false},"excerpt":{"rendered":"
Scenario I have been reading about the Full Text Search capabilities in SQL Server 2005 and your tips have been a big help to improve how we query our data.\u00a0 Thus far converting our core queries to leverage Full Text Search has been a big help.\u00a0 I have been seeing information about the FREETEXT command […]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[32,3],"tags":[156,157,155,21],"_links":{"self":[{"href":"http:\/\/www.codereview.co\/index.php\/wp-json\/wp\/v2\/posts\/299"}],"collection":[{"href":"http:\/\/www.codereview.co\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/www.codereview.co\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/www.codereview.co\/index.php\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"http:\/\/www.codereview.co\/index.php\/wp-json\/wp\/v2\/comments?post=299"}],"version-history":[{"count":4,"href":"http:\/\/www.codereview.co\/index.php\/wp-json\/wp\/v2\/posts\/299\/revisions"}],"predecessor-version":[{"id":365,"href":"http:\/\/www.codereview.co\/index.php\/wp-json\/wp\/v2\/posts\/299\/revisions\/365"}],"wp:attachment":[{"href":"http:\/\/www.codereview.co\/index.php\/wp-json\/wp\/v2\/media?parent=299"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.codereview.co\/index.php\/wp-json\/wp\/v2\/categories?post=299"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.codereview.co\/index.php\/wp-json\/wp\/v2\/tags?post=299"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}