due to ongoing performance problems with the known “many documents and reader fields” problem which is not solved - I use all known workarounds but there are still many issues - by 8.5.1 let me ask, if there will be any further investigations in using DB2.
I know, this is stoppped but my hope is, that there is enouph pressure from customer site to go on this path. Mybe not for mail but für customer applications.
Let me tell you that sql query views were the best feature I’ve seen for many years and I don’t understand why this will not be supported, escpeially since the funtionalty is there.
This is real life: My customer’s company policy is to remove local replicas for field sales and use online applications. Today I do not have any feasible solution for that.
Maybe there some IBM internal discussions with websphere sales realated to that feature???
Views haven’t gotten any true indexing enhancements in years. Well, there’s the “defer index build” feature which is more of an admin/disk space help (8.0), and also the feature where view index builds are integrated with the transaction log (6.0 I believe).
But the list of potential enhancements is huge:
store readers’ field info as part of the view index to help address the “many readers and docs” problem
add additional column totaling algorithms (min, max, stddev, “custom” with an @Formula would also be nice)
get view indexes out of the NSF, on an external path similar to DAOS’ functionality
cross-column totaling (e.g. a category row has a 12 in column A and 15 in column B. Column C shows 12/15)
use IBM’s patent from 2002 (which pertains to Notes/Domino specifically) to allow users to resort while inside of a category, or while using restrict-to-category
allow developers to specify fields to be indexed at the NSF level, similar to what “Optimize Document Table Map” does for the Form field (though that feature got broke in 6.0).