Tips for Running a Search

use the following suggestions to find the most accurate results search for words docid\ zfq1crnzud6t0pfkoiykusearch for numbers docid\ zfq1crnzud6t0pfkoiykusearch for phrases docid\ zfq1crnzud6t0pfkoiykuconsider your search words docid\ zfq1crnzud6t0pfkoiykucase sensitivity docid\ zfq1crnzud6t0pfkoiykunoise words docid\ zfq1crnzud6t0pfkoiykumultiple word search docid\ zfq1crnzud6t0pfkoiykuhyphenated words docid\ zfq1crnzud6t0pfkoiyku search for words search for exact words using quotation marks for example, if you enter "fail" , all records containing the exact word fail appear if you do not include the quotation marks, the results include exact words as well as similar words, such as fail , failing , or failed a word followed by an (asterisk) must match a prefix of some word in the results for example, b results in all records containing a word starting with the letter b inflectional generation is not supported for example, giv does not match gave some similar word searches might not work if the stem of the word matches a word in the noise word list (refer to noise words docid\ zfq1crnzud6t0pfkoiyku ) of your server database, such as out when searching for outlook , or in when searching for inbox records if you have this type of issue, try adding another letter to the search word, such as outl or inb when entering a search term search for numbers you can search for numbers in records by placing quotation marks around the numbers, such as "100" this returns all records containing the number 100 a purely numeric term (digits only, not alphanumeric) must match as a number you cannot search for partial numbers search for phrases you can search for records matching a phrase, such as "hard drive failure" or "system crash" enter the phrase in the text box between quotation marks this type of search allows you to narrow your results by placing strict limitation on the words or phrase used in the search by entering "print" with quotation marks, you will not get printer, printing, prints, and so on as the results exactly match your search phrase to find records containing words not in any specific order, do not use quotation marks consider your search words the more words you enter, the fewer results you get in return, but the results are a closer match to what you need not using quotation marks increases the number of records returned case sensitivity a microsoft sql database search is not case sensitive, which means that upper and lower case letters are treated the same with regard to a text search for example, bill or bill could return an item (bill) and the name of a person ( bill ) the database administrator is responsible for establishing how searches run on the database noise words noise words, also called stop words , are so common that they cause your search to return so many records that you cannot find what you were looking for noise words include a , and , by , can , for , is , no , not , the , to , and with itsm ignores noise words for example, if you enter "need to" , the application only searches for need because to is a noise word however, to is highlighted in the records returned multiple word search a multiple word search is one that uses more than one word in the search text box these are often referred to as boolean queries, which use boolean operators (such as and and or ) in a single phrase you can include both words with quotes and without quotes in a multiple word search by default, full text search uses or when multiple words are entered without a boolean operator the search results contain both words in no particular order the following are examples of multiple word searches search string results outlook or email all records that contain either word login outlook or email all records for outlook login and email login in no particular order outlook working all records that contains both words in no particular order hyphenated words common punctuation and separator characters are used as delimiters in tokenization the search matches only records where all search tokens match search tokens are wrapped in forms of (inflectional, \<search token>), which does not match with substrings therefore, hef does not match heft single letter search tokens are ignored for example, if the search is heft y , it will ignore the y common words, such as he are removed therefore carl he results in a single search token carl the token hef does not return results for heft , heftier , and heftiest instead, search using carl hef to get the matching records words separated by hyphens match, except that the matches must be in the same field of the results for example, quickly running matches any field that contains quick , quickly , quicker , and so on, as a word in the field and run , running , runner , and so on in the same field however, the words in the results do not need to be separated by a hyphen or in the same order