Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Current »

Full-text search makes searches in eDiscovery in message text or meeting transcripts more efficient and quick.

Overview

Full Text Search is designed to perform advanced text queries on character-based data in SQL Server.

  • It creates full-text indexes on columns containing textual data

  • supports complex queries such as phrase searching, proximity searching, and weighted searches

  • can be configured to use various languages and their specific linguistic rules

  • and is optimized for searching large amounts of textual data quickly and efficiently.

Full-Text Search Stoplist

Full-Text Search (FTS) in SQL Server uses a stoplist to ignore certain common words (stopwords) during indexing and querying. These stopwords are words that are considered to be of little value in a search because they are common in the language and are not helpful in narrowing down search results. The specific stopwords can vary based on the language used.

Common Stopwords in English

Some common English stopwords that FTS might ignore include:

  • Articles: a, an, the

  • Conjunctions: and, but, or

  • Prepositions: in, on, at, by, with, about, against, between, into, through, during, before, after, above, below, to, from, up, down, in, out, on, off, over, under

  • Pronouns: I, me, you, he, him, she, her, it, we, us, they, them

  • Others: is, are, was, were, be, been, being, have, has, had, do, does, did, will, would, shall, should, can, could, may, might, must

More details on managing stoplists can be found here:
https://learn.microsoft.com/en-us/sql/relational-databases/search/configure-and-manage-stopwords-and-stoplists-for-full-text-search?view=sql-server-ver16

  • No labels