I think it indexes individual columns only, and treats them as separate
fields... It does not combine column1 with column2, so firstname=john,
lastname=doe will not match john doe, but [EMAIL PROTECTED] will
match. Apparently (with SQL 2000 anyway) you cannot index computed
columns (first name +
I have used MS SQL Full-Text indexing. For building fairly intelligent
search engines based on data contained in a MS SQL 7, or MS SQL 2000
database it is not a terrible way to go.
You can manage the full-text indices via stored procedures so you can fully
automate working with the full text
Indeed, using SQL 2000 Full Text over Verity has some advantages :
- the SQL server box does the work of indexing/searching (whereas with
CF+Verity, it is usually done by the application server, which can take a
lot of ressources, unless you have a dedicated indexing/searching box),
- the biggest
3 matches
Mail list logo
