Continues to be vexing. Deleted and recreated the collection several times. Checked and repaired db for corruption. Changed the name of collection and reran. Upsized the data to SQL 2000, created a collection and did a CFIndex. All without effect.
Now I've got MM and the ISP talking. Going on 5 days now without the Verity service or a solution in sight. Thanks, Mark -----Original Message----- From: Richard Meredith-Hardy [mailto:rmh@;flymicro.com] Sent: Tuesday, October 22, 2002 1:17 PM To: CF-Talk Subject: Re: CFIndex for Verity quit working - Needs Attention by Macromedia! I had a problem something like this with a verity collection based on a DB with about 50,000 records which occasionally falls over after about 10,000 alterations (despite daily optimizations). A CFINDEX action = "PURGE" followed by a CFINDEX action = "REFRESH" usually fixes it but once or twice I have had to delete the collection completely and re-create and re-populate it. Ken Wilson wrote: > > I know nothing of the product but do recall a CF developer on another > list raving about dtSearch as a replacement for the version of Verity > packaged with CF. Might be worth looking at anyway: > > http://www.dtsearch.com/ > > Ken > > -----Original Message----- > From: Trey Rouse [mailto:trouse@;rice.edu] > Sent: Monday, October 21, 2002 12:51 PM > To: CF-Talk > Subject: RE: CFIndex for Verity quit working - Needs Attention by > Macromedia! > > Is it possible you are trying to index a recordset over 250,000 > records? > > The following is paraphrased from a Verity publication detailing the > Macromedia OEM agreement: > > Here is a list of key counts limits by product per Verity: > > ColdFusion Professional: 125,000 Documents Max. > ColdFusion Enterprise: 250,000 Documents Max. > ColdFusion Advanced: 175,000 Documents Max. > Coldfusion Developer Edition: 10,000 Documents Max. > > Features _NOT_ included with Macromedia's OEM agreement: > > 1. Brokered Search > 2. Does not have access to any of Verity's automatic classification > tools. 3. Does not support Relational Taxonomies. 4. Does not provide > integration with a company's chosen security context. 5. Does not > provide Verity's full document viewing capabilities. 6. Does not > provide Verity's recommendation engine. 7. Does not provide a > parametric search interface. 8. Does not provide hit count display for > categories or parametric attribs. 9. Does not provide Federated search > capabilities. 10. Does not provide Verity Gateways to content > management solutions. 11. Does not provide Verity Gateways to > enterprise e-mail applications. > > </verity> > > As you can see according to Verity, there is no limitation of the > Verity query language built into the Macromedia OEM agreement. Since > this document is provided by Verity when they are trying to sell K2 to > orgs that already have CFMX, I'm very confident that if sections of > the query language had been limited or smurfed as part of the oem > agreement, then Verity would have clearly stated this in big bold > letters ;). > > I think you can safely read into this that the fact specific functions > are not working in the CFMX verity implementation (like delete and > soundex), is most likely due to a mistake in packaging on Macromedia's > part. Someone from MM please address this thread! > > However, if there is indeed language level limitations in this OEM > product, Macromedia has a responsibility to its developers to make a > clear statement regarding exactly what is and isn't in this release! > > A few of you have asked for alternatives to the technology due to your > aggravation with this implementation. Here are my thoughts on the > matter: > > 1. For a large loose text/document search project I would recommend > purchasing Verity's K2 server. I would urge you NOT to judge the > Verity product based upon the oem experience delivered by the Verity97 > agreement with Allaire, and the K2 agreement with macromedia. > Verity's K2 is an extremely powerful product, and in my opinion the > best in the field, but it is priced as such. > > 2. Consider using some of the database free text search utilities. > Microsoft and Oracle both offer free text search utilities that run on > their DB engine. MS specifically has a SOUNDEX implementation in > their T-SQL implementation. This solution will place a considerably > heavier burden on you as the developer, but is perhaps a more cost > effective solution. You will likely never match verity's > implementation of thesaurus matching, and other really cool things > their engine does, but you can build a half way decent data centric > search. > > 3. Look into competing technologies. Inktome is also a good search > engine tool that you can license for your App. I haven't used them in > the last 18 months, but I know they used to offer a pay as you go > solution. .01 cents per query, etc. For a smaller load site this > could often also be a viable alternative considering the entry cost of > a K2 server. > > Good luck, > > Trey Rouse > Data Architect Developer > Rice University > > > -----Original Message----- > > From: Mark Leder [mailto:mel@;markleder.com] > > Sent: Sunday, October 20, 2002 1:16 AM > > To: CF-Talk > > Subject: CFIndex for Verity quit working > > > > Hi everyone, > > > > My client has an MS Access 2002 db which is periodically uploaded to > the > > ISP server (Win XP-CF 5) and a CFIndex Action="refresh" run on it. > This > > process has been used successfully for several months now. The db > when > > we started was about 4.5mb in size, now it's grown to about 11mb. > > > > The client does a compact and repair prior to uploading each time. > > > > The db only contains one table and one form, the table has an > autoindex > > numbering for each record (no duplicates), and three other > corresponding > > fields for each record (all memo fields). > > > > The problem is, the CF index has quit working on this database. I > have > > not changed a single line of code. The CFQUERY prior to the CFINDEX > > used to retrieve the db records works normally. > > > > The CFIndex hangs, and the Access db goes into a locked condition > > (db.lbd). This whole process used to take about 1 minute for an > > indexing routine, now it won't work at all. I've had the ISP reboot > the > > server but that doesn't help either. I've tried deleting and > recreating > > the collection, which works, but it doesn't solve the problem. > > > > Below is the dbrefresh.cfm code for your review. > > > > Any ideas on how to resolve? HELP!!! I'm really stuck. Is there a > file > > size limit that Verity won't work with if it exceeds that limit? > > (such > > > as it working with a 9mb file size, but not an 11mb file size). > > > > BTW: You're probably wondering, the client insists on working on > > the Access db on his client machine, then uploading to the server - > > he refuses to go to SQL 2000 if it means not being able to keep a > > copy at > > > his office. It's his life's work. > > > > > > <!---Query the database for each of the faq to get the various db > table > > fields--> > > <cfquery name="indexdb" datasource=#REQUEST.dsn2#> > > SELECT ask_ID, publication, keywords, abstract > > FROM oscar2002 > > </cfquery> > > > > <!---Index the contents of the query object using CFINDEX---> > > <CFINDEX ACTION="REFRESH" > > COLLECTION="citations" > > KEY="ask_ID" > > TYPE="CUSTOM" > > TITLE="publication" > > QUERY="indexdb" > > BODY="publication, keywords, abstract" > > CUSTOM1="publication" > > CUSTOM2="keywords" > > LANGUAGE="English"> > > > > Thanks, > > Mark > > > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4 Subscription: http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Structure your ColdFusion code with Fusebox. Get the official book at http://www.fusionauthority.com/bkinfo.cfm
