No doubt SQL Server 2005 has significant improvements on full-text search, as their own benchmark will tell. But to do the search, a developer needs to translate user's query into well-formed SQL queries. It's a vendor-specific language. And the full-text search has to run inside SQL Server, on the same computer.
So if your database volume goes up and you need to upgrade, you have to buy more licenses for a higher price, since you are bound to SQL Server. And you have to buy a more powerful computer, probably a high-end mainframe, for more CPU and memory resources.
- DBSight supports all JDBC-capable databases, including older versions of SQL Server that Microsoft ditched.
With the help from freedb.org, I posted our demo search to freedb.org's news page.
Currently, it's on the front page of http://www.freedb.org
I have just completed the tutorial on how to create a full-text search on freedb data.
The data quality is not really ideal. Since there are many duplicated entries and erroneous inputs. I am going to clean it later when I am free.
My goal is to show how easy it is to create a full-text search on your database.
The tutorial is here: http://www.dbsight.net/mediawiki/index.php?title=Step_by_step
The search is here: http://search.dbsight.com
There is a good article on Enterprise Search.
And another one: Why Writing Your Own Search Engine is Hard
Some marketing for DBSight:
Our aim is to enable administrators super easy to create a full-text search on any relational database, with better performance, and staying cheap.
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
Technical pet peeve: no search services are better than weak search services
In the comments, I saw this:
Fulltext searching on SQl2k is a pathetic joke
Now, you can determine yourself.
As you may notice, DBSight is based on the powerful Lucene package.
Here is an email archive on Lucene vs. MySQL Full-Text
We have a website!
We have come a long way to come to this. And we know there are two directions ahead of us.
One is to work harder to keep improving DBSight with the help from our users. The other is to blindly enjoy the short "success" and slide into disaster.
We choose the first direction. We would like to hear from YOU, our user, for any ideas, suggestions, and criticism.
If you find our product is somewhat helpful, but missed your expectations a little, let us know! We will try our best to make you happy!