Since the site’s inception, we’ve been massing large amounts of content on which millions of people have come to depend. We have numerous ways of getting to the content, but the quickest and easiest way to find specific information is to search for it.

AnandTech Search 1.0 (ColdFusion Verity)

The first version of the site used a search server included with ColdFusion named “Verity”. Most people have heard of Verity; they are one of the industry leaders in enterprise search software. The version of Verity that was included with ColdFusion back then was a light version of the full-blown Verity Search server. Although it did quite well at locating content via Boolean searches, it lacked flexibility and wasn’t all that of a performant.

AnandTech Search 2.0 (Microsoft FullText Search)

After we migrated to Microsoft SQL Server, we decided to use the Full Text search that is built-in to SQL Server. SQL Server Full Text came to be in version 7.0, and allows you to create catalogs that can contain multiple indexes on text column types. You can then configure Full Text to index the data in the background, or perform one time or scheduled indexing of the data.

There are, however, a couple of caveats with Microsoft Full Text search. The first is that it throws errors when your search criteria contain “noise words”. By default, Full Text search is configured with a list of “noise words”. Microsoft (and many other search engines) consider words like “because,been,before,being,between,both,but,by” to be common words that should not be contained in an index. Of course, you can trap this error easily in your application, but realistically, the search engine should just filter the words out of the search phrase itself.

The second and more important issue is how Full Text handles acronyms and numerical values in search strings. We never really did get to the bottom of the problem, but even with all of the noise words removed from Full Text, certain search phrases that contained acronym and numerical data wouldn’t return results. Since our data is full of technical acronyms and numerical model numbers, this was a major issue for us.

Along came Google
POST A COMMENT

48 Comments

View All Comments

  • Jynx980 - Monday, September 05, 2005 - link

    Interesting read, I don't understand a lot of it, but interesting none the less. Were you nervous cracking it open? I'd be sweating like Roger Ebert if I was trying to crack open a $3000 pizza box. Reply
  • Netopia - Monday, September 05, 2005 - link

    How long before we see a big brother for it caching the forums?

    Joe
    Reply
  • PorBleemo - Monday, September 05, 2005 - link

    Waaaay too much information in the forums. You would max out the higher-end model easily. Reply
  • Marlin1975 - Monday, September 05, 2005 - link

    Can you just not buy the software and install on your own hardware? Heck a 686b southbridge, does VIA even make those anymore, let alone SDRAM? That box must have had a lot of dust on it. Reply
  • coomar - Monday, September 05, 2005 - link

    so searching on anandtech is going to be using google search engine

    i didn't know microsoft was responsible for the engine used right now
    Reply
  • Verdant - Monday, September 05, 2005 - link

    i would hardly say microsoft was responsible... it was SQL server, but you can hardly say it is a search engine in a box Reply
  • bellwether - Thursday, November 29, 2007 - link

    Not that Google's search is much better (from a visual stand point). Heck, you had to have people develop http://www.components4asp.net/GoogleMini/">google mini add-ons so it could do things like show image previews and have a layout that doesn't look like a Google search. Reply
  • leexgx - Friday, December 21, 2007 - link

    adding an comment to this is fun when last post was like 2 half years ago heh Reply

Log in

Don't have an account? Sign up now