: 4400 | 106119 | 11884
|
: -4 : 2 : 6 |
Typically, there exist databases which have high informational value but long, even medium term retention may not be desirable.
What I'm proposing is for templated databases to be automatically deleted and re-created on a configured interval.
The typical scenario is databases like domlog.nsf, which provides invaluable insight into a website's usage patterns, bad URLs, data on external referers etc. On a high volume website, this database grows dramatically from day-to-day. Using the Archiving feature to delete documents is highly resource intensive making it inpractical.
LOG.NSF is another example. Compacting to relinquish unused space is impossible in this case without a server shutdown.
What I propose is a mechanism whereby Domino literally deletes and recreates specified databases on an interval, or on a size threshold, using it's internal mechanics to place a semaphore on such databases for the short procedure.
In the case of domlog.nsf, I am aware there are third party tools to analyse textual logging (ie not domlog.nsf), however I believe this functionality is fundamentally important for websites and should be internalised within Domino.
|
1) Peter Neidhart640 (14 Mar 2012)
So the log.nsf reaches its threshold, is deleted and recreated. And where are my log entries from this morning that I need to analyse a problem?
I feel it is a pretty stupid idea to delete the data. A better solution would be to rename the current database by extending the file name with a suffix like timestamp or a running number and then create a new empty database.
Then you are free to apply your own ways of handling this renamed databases.
I feel it is a pretty stupid idea to delete the data. A better solution would be to rename the current database by extending the file name with a suffix like timestamp or a running number and then create a new empty database.
Then you are free to apply your own ways of handling this renamed databases.
2) Mark Demicoli10094 (14 Mar 2012)
Yea good idea - then you could specify a mass storage drive to keep historic databases.
3) Vlad Sh10122 (15 Mar 2012)
Options replication of the properties of a database has the following settings: -> Space Savers -> "Remove documents not modified in the last (days)". Or I understand something wrong?
4) Chris Hudson433 (31 Mar 2012)
There are numerous options to remove old documents from databases. As Vlas suggested, replication settings are one way, With the log.nsf there is also a notes.ini setting to control how big the log gets.
See { Link }
See { Link }
5) Bill Malchisky8219 (24 Aug 2012)
I can see additional problems stemming from older DBs or users that have bookmarks to the DB and then call the help desk when they can't get their data. Unless you are just talking log DBS. Perhaps I am not seeing this, but purging an entire DB just to recreate it? Archiving like on the Journaling which automatically appends a suffix to the filename and makes a new primary DBs would be better.
Welcome to IdeaJam™
You can run IdeaJam™ in your company. It's easy to install, setup and customize. Your employees, partners and customers will immediately see results.
Use IdeaJam to:
- Collect ideas from employees
- Solicit feedback and suggestions from employees and customers
- Run innovation contests and competitions
- Validate concepts
- Use the power of "crowd-sourcing" to rank ideas and allow the best ideas to rise to the top
IdeaJam™ works with:
- IBM Connections
- IBM Lotus Quickr
- Blogs and Wikis
- Websphere Portal
- Microsoft Sharepoint
- and other applications.
IdeaJam has an extensive set of widgets and API's that allow you to extend and integrate IdeaJam™ with other applications.
Learn more about IdeaJam >>
IdeaJam developed by
