Hi,
Just a quickie… What’s the maximum number of documents you can have in a database before the views start to fall to bits?
Thanks!
Adam.
Hi,
Just a quickie… What’s the maximum number of documents you can have in a database before the views start to fall to bits?
Thanks!
Adam.
Subject: Max no. of documents you can have in a database?
No limit, up to the maximum size of a database.http://www-12.lotus.com/ldd/doc/domino_notes/7.0/help7_designer.nsf/855dc7fcfd5fec9a85256b870069c0ab/a6e2e6d3f89a44ce8525704a003f35aa?OpenDocument
Designer help (up to 6.5) used to include the information, that the number of documents in a view was limited to “Maximum of 130MB for a view index”. Experience showed, that this was incorrect even for R5.
Ben’s list of known Domino limits
gives some more details on this topic and states, that the maximum size of a view index is really 128 GB. However, since this is above the maximum size of a database, the information in Designer 7 help is correct.
Subject: RE: Max no. of documents you can have in a database?
Thanks!
Is there any practical limits on it, i.e. you can have 128GB but any views over 2gb get really slow, for example?
Many thanks again. Very much appreciated.
Adam.
Subject: RE: Max no. of documents you can have in a database?
There is no possible way to answer that. It’s going to depend on the number of views, the compexity of view selection and column formulas, the number of sorted/sortable columns, whether you are using readernames fields, whether you are hiding empty categories, and maybe other things I’m not thinking of off the top of my head – plus, the volatility of your data, and then of course there’s the power of your hardware to consider. If you’re talking about 128 GB databases and 2 GB views, it sounds like you’re probably going to be pushing the envelope in ways that few people have ever tried. Even minor differences in your environment and requirements may have major consequences, making comparisons to anyone else’s experience invalid. So, your best bet is to start mocking up some test databases and loading them with test data and put them through some paces on hardware that matches your production environment. I’m afraid there are no shortcuts for this.