Collection of full-text retrieval of SQL Server 2

The query clause only contains ignored words.

This is because some simple words, such as "yes", are used for queries.

The solution is to clear c: \ Program Files \ Microsoft SQL Server \ MSSQL \ ftdata \ sqlserver \ config \ noise. CHS

I think this method is not advisable. You can open this file and find the following words: Is, are, be, at, I, yes

These words are frequently-used words and have little significance in queries, as if there are paper scraps in almost every drawer. indexing these words is not worth the candle, therefore, the full-text engine calls these words as interfering words without indexing. I personally think it is better to filter these words in the application and then give the user a friendly prompt, instead of clearing noise. CHS treats the full-text engine rudely. For example, you can search for "of" in Google"

In addition, thanks to ghj, a very important thing is missing. Unlike the normal index immediate update, full-text indexes generally maintain indexes on a regular basis, so it is inappropriate for frequently updated data, the objects that require full-text indexing are generally paper webpages and so on. It is suitable for pulling!

I personally think that my database is not representative, so I will not elaborate: When indexing, the CPU and memory usage are very high and the time is also very long (my database is used throughout the night below ), after completing the query, you do not need to use a lot of system resources. When multiple full-text queries are concurrent, there is a lot of CPU consumption, but it is better than like.

The database on my system is 123 m, which is too small and does not have any special advantage in using full-text indexes. However, you can think about the massive data volumes like Google, it is unimaginable to use like: Of course, no one else uses relational databases.

---------------------------------------------------------------------- Transferred from "cat's nest in carfield"