> > > Duh Verity I forgot about that. But still wouldnt the back > > > end of sql be alot faster than cf verity? > > > > No, there's no reason for it to be that way. The K2 server > > is pretty fast. In addition, you can offload K2 search > > functionality onto a separate machine from your web and > > database servers. > > no caching. can't join back to the indexed table. can't > combine with other WHERE clause stuff. sql server text > indexing beats the pants & socks off of verity.
Well, I know you like the SQL Server text indexing quite a bit, but in fairness, these aren't serious issues in most of the search functionality I've seen. You're free to cache what you like, after it comes back from Verity, for example, by sticking it in a memory variable, although I don't know how reusable that would be. In addition, Verity K2 has its own internal caching, although I have no idea how it works, or how well it works compared to that of SQL Server. As for joining back to the indexed table, you're right, although in most cases I'm not sure I'd want to join back to that table - I just want to show the results in a drill-down interface, and let the user pick a record before fetching more information. Even if I did want more information right away, it's pretty trivial to simply query the database using the Verity keys. The same goes for combining it with other WHERE clause stuff; you can just query the database using the Verity keys and the additional filtering clauses that you want. I admit that, given a choice, I might go with SQL Server's indexing, but I don't know whether I'd justify purchasing SQL Server for a project for that reason alone, when Verity provides most of the functionality that the project might need. In addition, Verity can do some things that I don't know whether you can do in SQL Server's text indexing, like spidering sites and indexing filesystem contents (although I suspect that if one knew enough about SQL Server's full text indexing, it could easily be combined with NTFS full text indexing since they use the same underlying engine. Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ voice: (202) 797-5496 fax: (202) 797-5444 ______________________________________________________________________ Structure your ColdFusion code with Fusebox. Get the official book at http://www.fusionauthority.com/bkinfo.cfm FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
