I would welcome opinions on whether FTS would help in our scenario.
The table has about 28 million rows and has about 10,000 rows added every
morning in an intensive batch process. Then another batch query process is
run that looks for partial name matches.
Eight of the fields we query against are char or varchar, all with single
words.
Sample query: SELECT casenumber FROM table WHERE fname LIKE 'j%' AND lname
LIKE 'smi%'. Rreturns 55,874 rows in 7 seconds in QA.
I am also concerned about time to populate FT index every day.
Machine is dual Xeon 3.2 with 4GB ram, OS on RAID1 & SQL data on RAID5. Win
2003 Server and SQL2000, with SQL2005 later this year.
Thanks much!
Hilary Cotter - 26 Jan 2006 19:37 GMT
Wow! That's fantastic speed for a like. I'd try change tracking. IIRC on a
similar machine I was able to hit 2000 rows per minute with SQL 2000.

Signature
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
>I would welcome opinions on whether FTS would help in our scenario.
>
[quoted text clipped - 15 lines]
>
> Thanks much!
Bil Click - 27 Jan 2006 16:03 GMT
Thanks Hilary, but do you think a Full Text search would be faster searching
on single words?
> Wow! That's fantastic speed for a like. I'd try change tracking. IIRC on a
> similar machine I was able to hit 2000 rows per minute with SQL 2000.
[quoted text clipped - 18 lines]
> >
> > Thanks much!
Hilary Cotter - 27 Jan 2006 19:37 GMT
It will be for larger tables. I am not sure where the cut off it - i.e.
20,000 rows or 2 million.

Signature
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
> Thanks Hilary, but do you think a Full Text search would be faster
> searching
[quoted text clipped - 27 lines]
>> >
>> > Thanks much!