Technical pet peeve: no search services are better than weak search services

re: Technical pet peeve: no search services are better than weak search services

KonnienL — Sun, 27 Dec 2009 07:40:58 GMT

Very good topic referring to this post. One can check the article at the papers writing service and <a href=" http://www.supremeessays.com">buy essay</a> and already written essay done by essay writers.

DBSight is a better alternative to "Fulltext searching on SQL2k"

TrackBack — Thu, 14 Apr 2005 15:56:00 GMT

Admittedly, I haven't used full text search on SQL 2000. 
But I am sure DBSight can beat it.
I have seen posts like this 
<a href="http://weblogs.asp.net/jasonsalas/archive/2004/02/11/71130.aspx">Technical pet peeve: no search services

re: Technical pet peeve: no search services are better than weak search services

Sassy — Wed, 23 Jun 2004 22:33:00 GMT

Fulltext searching on SQl2k is a pathetic joke. Not because of CPU cycles, because it _simply _dont _work. Once again, garbageware from Microsoft

re: Technical pet peeve: no search services are better than weak search services

Jason Salas — Wed, 11 Feb 2004 23:59:00 GMT

Hi guys,

Good thoughts. I'm pondering moving to FTI myself, but in doing so I'll need to migrate the entire SQL Server DB we use now (only about 9,000 records, with multiple NTEXT fields) to a different database server.

Has anyone seen any creative alternatives to using a good classical search?

re: A Case for Search.Microsoft.Com

TrackBack — Wed, 11 Feb 2004 15:53:00 GMT

re: Technical pet peeve: no search services are better than weak search services

Derick Bailey — Wed, 11 Feb 2004 14:24:00 GMT

The actual indexing may take some cycles, but it only happens on the schedule that you set. Any good DBAmin should know how to setup the schedule to run during the lowest traffic times, and create a good fulltext index for searching.

As for the actual fulltext searching in SQL Server 2K, it's actually part of Indexing Service that gets called to do the searching. If someone complains about SQL 2K fulltext, but also uses the Indexing Service, then that person is full of crapp.

I personally think that the fulltext searching in SQL2K is quite nice. But then, I actually spent a few minutes to write a query parsing engine that builds proper fulltext search queries based on user input.

re: Technical pet peeve: no search services are better than weak search services

Wallym — Wed, 11 Feb 2004 10:46:00 GMT

Jason,

The reason that I see why they aren't using FreeText and such is that MS's fulltext engine in Sql2k is not very good. It takes an amazing effort on the part of the CPU to get it working. Yukon's full text engine is suppossed to be much improved.

Wally

Creative alternatives to the poor search feature conundrum (low budget or otherwise)

TrackBack — Wed, 11 Feb 2004 09:37:00 GMT