问题描述
我们正在努力为我们的客户网站，我们希望采取可以很容易地重复使用的搜索解决方案。哪一个我们应该去后？如果我们使用谷歌搜索API，还是应该使用MS SQL Server全文索引和CONTAINS和放大器; FREETEXT predicates？
We are working on websites for our clients and we want to adopt a search solution that can be easily reused. Which one should we go after ? Should we use Google Search API or should we use MS Sql Server Full Text Indexing and the CONTAINS & FREETEXT predicates ?
推荐答案
我们在这里使用SQL Server全文索引的堆栈溢出和它的作品相当不错 - 但我的只有的建议是在2005年至2008年，该版本中，我们使用它。我听见它在2000年更糟糕有怪癖（禁用词列表等），但并不严重。它的快速和做什么它在锡说，大部分。
We use SQL Server full text indexing here on Stack Overflow and it works reasonably well -- but I can only recommend it for 2005 and 2008, the versions we use it on. I heard it's much worse in 2000. There are quirks (stopword lists, etc) but nothing serious. It's fast and does what it says on the tin, mostly.
您遇到的问题包括（）和自由文本（）是用户往往期望搜索在整页的水平，ALA谷歌，其中任何被写在页面/屏幕搜索。这不是真正的数据库是如何工作的，但用户并不关心这个。他们关心的是结果，并有（可以说是合理的）期望基于多年网络搜索的。
The problem you run into with contains() and freetext() is that users often expect to search at the "whole page" level, ala Google, where anything that's written to the page / screen is searchable. That's not really how databases work, but users don't care about that. They care about results and have (arguably reasonable) expectations based on years of web searching.
如果您希望在需要整个页面的搜索水平，我强烈建议在看的或 Lucene.NET （假设你基于SQL的使用微软堆栈）。
If you expect to need the "whole page" search level, I'd strongly recommend looking at the Google Search API, or Lucene.NET (assuming you're a Microsoft stack based on use of SQL).
这篇关于谷歌搜索API与MS SQL Server全文索引？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！