I'll admit that I've never had a need to work with user index objects to this point, but I do not think you will find it to be nearly as robust as DB2 access path index... I suspect that, by the time you build up enough functionality to routinely use USRIDX in your applications, that the additional overhead and complexity would negate most of the performance gains.
JMO,
-Eric DeLong
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of gn pr
Sent: Monday, January 07, 2013 1:25 PM
To: midrange-l@xxxxxxxxxxxx
Subject: managing user indexes (*USRIDX)
Hi,
Which is the best way to use the user indexes (*USRIDX)? Due to user indexes are faster access than a database file, is there any native way to manage multiple user indexes? By example if I have one user index and 3 replicas from it, is there a 'native' (triggers, links, something…) way to manage the access or chose one of this user indexes to get the data?
My idea is manage the user indexes as a distributed database taking advantage of the fast access, is it possible with the tools provided from IBM?
--- Grace Pahuasi---
