You need have MS Index Server installed. For NT it comes with the option pack, not sure about 2000. Once installed you have the standard MMC interface to specify which directories to index, and that's it. Don't have to reindex like you do with Verity it's handled for you. You need to set up full-text in SQL Server and then specify the catalogs you have set up within the database you want to use it in, then you can write sql statements combining tables and catalogs. Good info on doing this on MS site e.g. http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnduwon/htm l/d5dbsearch.asp
-----Original Message----- From: Mark A. Kruger - CFG [mailto:[EMAIL PROTECTED]] Sent: 13 March 2002 14:40 To: CF-Talk Subject: RE: A Verity SQL Combo Question - Can this be sped up? Kevan, Could you give a short summary of how one uses MS indexing? I'd be very interested. Thanks! Mark -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Wednesday, March 13, 2002 3:29 AM To: CF-Talk Subject: RE: A Verity SQL Combo Question - Can this be sped up? Could try using MS indexing instead of Verity, I've found it better anyway. -----Original Message----- From: Mallory Woods [mailto:[EMAIL PROTECTED]] Sent: 08 March 2002 16:13 To: CF-Talk Subject: A Verity SQL Combo Question - Can this be sped up? Greetings all.. We have an interesting verity search/SQL search issue and I was wondering if anyone has any hints on how this possibly could be sped up.. Ok.. some background.. The Keyword search is done in verity and its fast by itself.. The other searches are fast and are regular SQL.. when they are both combined they take a long time.. Here's what happens.. The Verity search returns the Keys which are equal to the ID field in the SQL DB.. if the keyword field is not blank then it add the keys in to the main query example query.. -- SELECT EPSTable.posting_date, agency_, office_, classcod_, subject_, solnbr_, epsid, (select top 1 par_id from par where rfpnumber=replace(epstable.solnbr_,'-','') and (rfpnumber is not null or rfpnumber<>'' or rfpnumber<>'N/A')) parid FROM EPSTable WHERE (1 = 1) AND EPSTable.epsid IN (13913,11967,15428,15407,15057,15036,18538,14881,19636,18330,9411,16568, 7593,19812,19391,17230,16774,10795,13469,6393,11616,11293,18112,16529,15 461,15090,13871,11925,10778,9032,17558,16233,13893,13310,13069,11947,107 79,9771,8907,7441,2676,16772,12398,10547,7974,5239,4158,20497,20400,2039 9,20051,19996,19804,19640,19610,19299,18582,18300,18299,18291,18258,1812 3,18075,17862,17738,17111,17026,17014,16993,16982,16846) AND CLASSCOD_ = '10' ORDER BY POSTING_DATE -- As you can see it returns a whole lot of Keys which are included in the query.. this slows the whole query down.. We have the DB indexed and have tried other things to speed this up.. any suggestions on getting this going faster? Thanks in advance.. Mallory Woods INPUT Inc ------------------------------------------------------------ ______________________________________________________________________ Get Your Own Dedicated Windows 2000 Server PIII 800 / 256 MB RAM / 40 GB HD / 20 GB MO/XFER Instant Activation � $99/Month � Free Setup http://www.pennyhost.com/redirect.cfm?adcode=coldfusionb 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
