(maybe I should change the subject to "Eloquence-to-SQL replication")

Connie wrote:

> Our IMAGE db's are so designed as to give great access times, except 
> when we're trying to look for a value imbeded within a non-indexed 
> field.  (Yes - we used Omnidex for awhile - )
> 
> We're using a SQL db on some web projects - much smaller set of records, 
> and works fine.

Your "subset" example somehow reminds me that -at least in some
use cases- it might be feasible to "replicate" selected parts of
an Eloquence database to another type of data store by using the
"forward logging" and "auditing" features...

  http://www.hp-eloquence.com/support/B0710/doc/index.html

The "forward logging" (somewhat similar to TurboIMAGE logging)
captures database changes to logfiles, which can also be enabled
for use in conjunction with the fwaudit utility, which in turn
allows to extract (selected) subsets of the changes for review
or further processing.

This could be used to populate/feed/update another database,
SQL or whatever. Not a "real time replication", but depending
on the setup (eg frequency of logfile switches and extracts)
something like once per day or once per hour sounds feasible.

Just a thought ;-)

Lars.

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *