We've recently implemented indexing into our application as a
replacement for our own custom indexes, so I'm at least a little bit
qualified to answer some of your questions:


* Number of indexes - no guidelines afaik. The update process seems fast
enough - certainly, every write triggers an index update even if the
indexed attribute(s) hasn't changed. I would say the cost in update time
vs index benefit will be file-specific, depending on how much the file
is written to and how often it is searched.

* Never used build.index / online.

* Consistency - no problems yet.

* Indexing mv / svs - no problems here. We've used some fairly complex
dictionary items to build up the index keys. Basically it doesn't matter
how the index key is built up providing it comes from @RECORD - although
we've used remote files in one or two cases in the knowledge that they
are unlikely to change.

* ECM - never used it

* Corruption - not hit this one yet. But it's obviously a concern.

* Benefits - as I said above, the indexes are replacing an amount of
existing code, although I've had to write more code to fully integrate
the indexes with our search front end. However overall it's lead to a
simplification in the code base and faster / better search behaviour,
with various quirks in the original code gone.

We've also considered using indexes in a more general sense for selects
and there's an idea floating around to measure the speed of the selects
and the select commands as our system is used out in the wild; we can
then use this information to index those specific dictionary items that
would give the biggest improvements.

Hth

Ed


-------------------------------------------------------------------------------------------
Please remember to recycle wherever possible. 
Reduce, reuse, recycle, think do you need to print this e-mail?
-------------------------------------------------------------------------------------------
This e-mail and any attachment(s), is confidential and may be legally 
privileged. It is intended solely for the addressee. If you are not the 
addressee, dissemination, copying or use of this e-mail or any of its content 
is prohibited and may be unlawful. If you are not the intended recipient please 
inform the sender immediately and destroy the e-mail, any attachment(s) and any 
copies. All liability for viruses is excluded to the fullest extent permitted 
by law. It is your responsibility to scan or otherwise check this email and any 
attachment(s). Unless otherwise stated (i) views expressed in this message are 
those of the individual sender (ii) no contract may be construed by this 
e-mail. Emails may be monitored and you are taken to consent to this 
monitoring.  

Civica Services Limited, Company No. 02374268; Civica UK Limited, Company No. 
01628868
Both companies are registered in England and Wales and each has its registered 
office at 2 Burston Road, Putney, London, SW15 6AR.
-------------------------------------------------------------------------------------------

_______________________________________________
U2-Users mailing list
U2-Users@listserver.u2ug.org
http://listserver.u2ug.org/mailman/listinfo/u2-users

Reply via email to