views:

661

answers:

6

Are there ways to get around the upper database size limit on Notes databases? We are compacting a database that is still approaching 60 gigs in size. Thank you very much if you can offer a suggestion.

+2  A: 

Just a stab in the dark:

Use the DB2 storage method instead of to a Domino server?

Martlark
Thanks I'll pass it along
Todd
You can use DB2 to store the notes database instead of the domino server, but the code of the Notes app stays the same.
Martlark
+3  A: 

Even if you could find a way to get over the 64GB limit it would not be the recommended solution. Splitting up the application into multiple databases is far better if you wish to improve performance and retain the stability of your Domino server. If you think you have to have everything in the same database in order to be able to search, please look up domain search and multi-database search in the Domino Administrator help.

  • Maybe some parts of the data is "old" and could be put into one or more archive databases instead?

  • Maybe you have a lot of large attachments and can store them in a series of attachment databases?

  • Maybe you have a lot of complicated views that can be streamlined or eliminated and thereby save a lot of space and keep everything in the same database for the time being? (Remove sorting on columns where not needed, using "click on column header to sort" is a sure way to increase the size of the view index.)

Mattias Kihlström
Thanks I'll pass this along
Todd
+1  A: 

I'm guessing that 80-90% of that space is taken up by file attachments. My suggestion is to move all the attachments to a file share, provided everyone can access that share, or to an FTP server that everyone can connect to.

It's not ideal because security becomes an issue - now you need to manage credentials to the Notes database AND to the external file share - however it'll be worth the effort from a Notes administrator's perspective.

In the Notes documents, just provide a link to the file. If users are adding these files via a Notes form, perhaps you can add some background code to extract the file from the document after it has been saved, and replace it with a link to that file.

Ken Pespisa
Thanks, I'll email my manager this info!
Todd
+1  A: 

I'm assuming your database is large because of file attachments as well. In that case look into DAOS - it will store all file attachments on filesystem (server functionality - transparent to clients and existing applications).

As a bonus it finds duplicates and stores them only once.

More here: http://www.ibm.com/developerworks/lotus/library/domino-green/

Frode
+1  A: 

If the issue really is large file attachments, I would certainly recommend looking into implementing DAOS on your server / database. It is only available with Domino Server 8.5 and later. On the other hand, if your database contains over 100,000+ documents, you may want to look seriously at dividing the data into multiple NSF's - at that number of documents, you need to be very careful about your view design, your lookup code, etc.

Some documented successes with DAOS: http://www.edbrill.com/ebrill/edbrill.nsf/dx/yet-another-daos-success-story-from-darren-duke?opendocument&comments

Ed Schembor
Thank you. Much appreciated.
Todd
+2  A: 

If you're database is getting to 60gb.. don't use a Domino solution you need to switch to a relational database. You need to archive or move documents across several databases. Although you can get to 60gb, you shouldn't do it. The performance hit for active databases is significant. Not so much a problem for static databases.

giuliocc
How does using an RDBMS help when the original system is not relational?
Ben Poole