Hmmm, will the client not accept an index optimization to be done
instead of
a full rebuild? A full rebuild is always going to be an insanely long
running process when there are that many objects involved, which makes
things difficult if it's a live production box. All i can say is, if
it's a
full rebuild that they want, it should prolly be done on another box
that is
not live, and when it is finished, copy it across to the live box...
Internally, we update incrementally every hour, and optimize every
night, it
works a treat, we have had a high volume production box doing this
for weeks
without a hitch.
Cheers,
Aaron
-----Original Message-----
From: Stephen Collins [mailto:[EMAIL PROTECTED]]
Sent: Thursday, 19 July 2001 4:43 PM
To: Spectra-Talk
Subject: RE: Large object sets, lots of data, Verity and memory
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Aaron
We ALREADY do incremental updates automatically as well. A script
goes and looks each hour for updated objects within the last hour and
does what you've suggested. It works a treat as it only updates a
few objects at a time.
The script causing me problems is a weekly full rebuild of the
indexes the client has requested on the basis of their worry that
incremental index updates will ultimately make the index work at a
less than optimal level. I don't really know whether this is valid
or not, but it's a deliverable.
Steve
========================================================
Stephen Collins, Technical Consultant - ACIS (Australia)
Work : [EMAIL PROTECTED] Personal : [EMAIL PROTECTED]
ICQ UIN : 56321783 Yahoo! : trib
"Before I got into triathlon, I was a normal person."
> -----Original Message-----
> From: Aaron Shurmer [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, 19 July 2001 4:30 PM
> To: Spectra-Talk
> Subject: RE: Large object sets, lots of data, Verity and memory
>
>
> Stephen,
> Just a side note, I hope you are locking the application var reads,
> or making sure that there are never any writes taking place after
> the first
> application hit takes place, or this could corrupt, but anyway.
>
> Have you though of doing your verity updates incrementally, like,
>
> ************
> <cfquery name="qGetObjects"
> datasource="#Request.cfa.datasource.dsn#"> select objectid
> from objects
> where typeid = '#typeid#'
> and DATETIMELASTUPDATED > '#lastIndexUpdate#'
> </cfquery>
>
> <cfif qGetObjects.recordcount>
> <cfset lobjectids = valuelist(qGetObjects.objectid)>
> <cfa_typeindexkeyupdate typeID="#typeid#"
> lObjectIDs="#lobjectids#"
> dataSource="#Request.cfa.datasource.dsn#">
> <cfa_metadataindexupdate lObjectIDs="#lobjectids#"
> datasource="#Request.cfa.datasource.dsn#">
> </cfif>
> ************
>
> This will update the verity index for every object updated since
> the last
> time the update was run, all you have to do is store the last
> updated time
> to file, and off you go, you may also wish to make the
> lastIndexUpdate =
> lastIndexUpdate - 1 hour or something to pick up changes that took
> place
> while the script is running...
>
> Hope that is of some use.
>
> Cheers,
Aaron.
-----BEGIN PGP SIGNATURE-----
Version: PGP Personal Privacy 6.5.8
iQA/AwUBO1X01n65o/U9+lJVEQIA5gCfe9yOiwVvHfp13snvV/CQ1GPvgYoAnido
iKO0y0i+K/NgH6EyIXuqa5b2
=EuGw
-----END PGP SIGNATURE-----
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
------------------------------------------------------------------------------
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/spectra_talk or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
