IdeaJam(tm) RSS Feed

Notes Client / Other: Notes Maintenace Application

Fri, 18 Jan 2008 03:38:35 +0000

Author: Henry Ferlauto
Tags: compact notes client fixup updall
Idea:

Create a small, end-user friendly applciation to essentially run all of the "n*.exe" programs in the Notes program folder.

In particular, the abiltiy to run "the big three" maintenance applications against one's local databases:

(1) Fixup

(2) Compact

(3) Updall

If you want to go for broke, add a scheduling utility (think: anti-virus and anti-spyware software) that can perform the operations at a specified time, and have the ability to shutdown the Notes client, if running.

Domino Administrator / Other: Report Status of compact/updall/fixup when done

Fri, 14 Dec 2007 05:49:12 +0000

Author: Nathan Chandler
Tags: status indictor report progress compact fixup updall
Idea:

When initiating a compact/fixup/updall command it would be great to get an idea if the task completed successfully, or was interrupted, had errors, or even how far along it was. Watching the console and scanning through millions of lines to look the status is well, painful - especially if it's a large database.

Notes Client / Other: File maintenance policy

Wed, 25 Mar 2009 12:12:00 +0000

Author: Mike Rosenbaum
Tags: compact CACHE.NDK fixup updall
Idea:

It would be nice if there were a desktop poilcy that woiuld perform regular file maintenace on Lotus Notes databases. I have been using it since version 4.6.5 and we have many users who have been through 3 -4 upgrades. Unless I touch their workstation and run manual compacts, fixups or updalls the Lotus Notes clients never get looked at. It would be nice if there were a policy that would cause the workstation to run file maintence on a regular basis. I would prompt the user that file maintenance was going to be done and it would run in the back ground.

Another feature would be to have the CACHE.NDK file deleted on a regular basis. I have noticed that when your CACHE file gets to be around 30 MB or larger the client starts misbehaving. If there was a parameter that would check the size of the CACHE file on start up. If it is over 30 MB delete it and have the system recreate it. Another option would to be to have it recreated on a regular interval