One of the most well-known inquiries I get about Notes Domino organization is: “How might I find unused Notes Domino information bases?”
Associations regularly have several Notes/Domino information bases across numerous workers, a couple with massive utilization. Finding and eliminating new Notes/Domino information bases diminishes circle space and unpredictability for the two clients and overseers.
The patterns worker errand can assemble this information for you, and you can see it in the activity.NSF or inside the Domino Administrator customer (at Server – > Analysis – > Activity).
In any case, the patterns task – and other comparative information gathering strategies – have a disadvantage. You should empower the insights gathering, trust that the information will be gathered, and examine the report afterward. Consider the possibility that you need to think about Notes/Domino information base utilization in recent months. It would help if you thought back as expected, not sit tight a half year for new information.
The Database Catalog (catalog. NSF) has the data you need. Yet, the practical realities are covered inside the index records and are unwieldy to peruse. Without much of a stretch, you can open up an individual inventory archive for a specific information base and see its utilization. However, you genuinely need a report that shows a rundown of the apparent multitude of information bases in your undertaking, with the most un-utilized at the top.
I’ve made two perspectives that give you merely such a report, and you can add these perspectives to your Database Catalog, making it altogether more valuable. An example information base containing the views – named “Information base Usage Report” – is on my Web website’s Downloads page.
The principal see shows:
•The number of employments for every information base during the most recent month
•The number of employments per information base during the “report period.”
•The length of the report time frame in days
The reporting period is when the Database Catalog assembled information for that Notes/Domino data set. Remember that if the report time frame for an information base is short (say, under seven days), the use of information is likely, not reliable.
The subsequent view encourages you to center around Notes/Domino information bases that can cause expulsion from the framework. The picture shows just information bases where the report time frame is more prominent than 20 days, so it disposes of untrustworthy information. The view is arranged by use every month, so evacuation competitors are at the top. Finally, the last segment shows the managers and Designers of the information base (taken from the ACL) since you might need to contact these individuals before erasing their information bases.
Actually, the perspectives work by choosing components from the use exhibit that is put away inside each inventory archive. For instance, the seventh component of the field DbActSummDisp is the number of employments for that information base during the most recent month. The goal that sees section contains the recipe DbActSummDisp.
In like manner, DbActSummDisp is the number of days in the report time frame. Since the exhibit component sentence structure (square sections) was presented with Notes/Domino 6, these perspectives don’t chip away at Notes/Domino R5 or prior.
The director and planner segment is relatively trickier because the names are covered inside two fields – ManagerList and DesignerList.
You can utilize this example in two different ways:
•Copy/glue reports from your catalog.NSF information base into my example data set
•Copy/glue the two perspectives from my example into your worker’s catalog.NSF