Urs Meli

350 views? Might want to take a look at the application structure to see if that many views are really necessary... performance would typically be negatively impacted even without introducing DB2 into the environment.

Hi Tim

There are lots of personalized views. The performance issues are the reason, we are looking at a db2 integration. Because of the query views, we could replace the personalized views completly.



kind regards

urs

I took a sales management db to db2 backend and was able to remove 180 views. I built an embedded view that let the user select how it was categorized and what columns displayed what along with some pre-defined selections. I was able to use one queryview. The support app was easier since it was web enabled you can use the paramters passed to the view to build the query statement. These were both in the 20gb range with over 100k documents. make sure you have enough resoucres and let it have time to build views. I cleared all views with the admin client then left it for a weekend.

I got the error only on 2 views, which in work perfectly on a domino server. It has to be one or more columns.

In the designer client everything is all right. As soon as I open it in notespreview or in the notesdatabase, the error appears. grrrrrr

Yesterday I removed some columns and suddenly the view worked. Now there are only 10 columns. Original view had about 20 columns.
Great. Adding or copying a new column -> index corrupt... grrr.