Chat now with support
Chat with Support

MessageStats 7.8 - Report Pack for Lotus & IBM Notes User Guide

About the Lotus and IBM Notes Report Pack Preparing for Installation Configuring the Report Pack Database Management Setting Task Default Properties Creating Gathering Tasks Using the Reports Console Lotus and IBM Notes Report Descriptions Report Filter Definitions

About the MessageStats Database

The MessageStats Database stores the data that is used to render reports.

When you install the report pack, you provide the location of the database server. MessageStats stores that location and displays the location on the Database tab of the MessageStats Server Properties dialog box.

Supported Database Implementations

There are two database server implementations that you can use to store the collected data:

•
For evaluation and test purposes, you can use SQL Server Express.Server
•
For production use, use SQL Server 2012, SQL Server 2014, SQL Server 2016, or SQL Server 2017,

You can also employ a distributed database implementation.

Managing your MessageStats Database

The MessageStats Database stores the information that is used by the reports. When the database is properly tuned, information can be efficiently stored, and the reports can quickly access the required data. Over time, the database will grow, and the database server may become taxed. However, it is critical that the database retain enough data for any historical reporting needs that may arise.

Proper database management includes following the Microsoft best practices for backing up data and archiving historical data. To manage your database, you can use the Database Management functionality to selectively delete obsolete data and to tune the database for optimal performance.

Using Database Management

During the installation of the Lotus and IBM Notes report pack, additional tables are added to the MessageStats database in order to store Note-specific data. MessageStats allows you to manage the storage of Lotus and IBM Notes object data to prevent excessively rapid growth of the MessageStats database.

In MessageStats, database management functionality is extended to include database management functions specific to Lotus and IBM Notes data. Using Database Management, you can delete obsolete information and tune your database.

Before you modify your database, ensure that no consoles are currently writing information to the database. If you use Database Management while a console is writing to the database, you risk corrupting your database.

To access the Database Management tool
•
Select Database Management from the treeview.

The Database Management tool provides the following functionality:

•
Database Aging (For more information, see Configuring an Aging Task .)
•
Database Maintenance (For more information, see Database Maintenance .)
•
Deleting Data (For more information, see Deleting Lotus and IBM Notes Object Data .)

Configuring an Aging Task

You can use the Data Aging function to delete the historical data from your database. The Lotus and IBM Notes Configuration option under the Data Aging node allows you to define the aging task for Lotus and IBM Notes data.

To define a data aging task
1
Expand the Database Management | Data Aging | Lotus and IBM Notes Configuration nodes in the treeview.
2
Select Delete aged data.
3
Select Age Statistics (days) check box.
4
Enter the number of days you want to retain statistical data in your database.
5
Click Configure Job.
6
Select Daily, Weekly, or Monthly to indicate how often you want to delete the data older than your retention definitions.
Depending on the schedule type that you select, the bottom box changes to an appropriate interval selector.
7
Enter the Start Date and Start Time information.
8
Click to select the Limit Job Execution Time box if you want to limit the time duration for an aging job, and enter an end time.
9
Enter an appropriate recurrence interval:
•
Enter the number of days between jobs for Daily schedules.
•
Enter the day of the week for Weekly schedules.
•
Enter the day of the month for Monthly schedules.
10
Click Deploy.
Data Aging Job History

After you create a job, the interface changes to a three-tab format:

•
The Schedule tab contains the same content as the Create Job tab had before a job was created.
•
The Properties tab describes the properties associated with the aging job, and is updated as new information becomes available.
•
The History tab contains a log of past aging jobs
Logging the Aging Progress

Because the aging process is performed by a service, progress is recorded in the log journal for all database management activities.

The log information is available in the MessageStats log journal, so activity can be viewed on the MessageStats Gathering reports by filtering the Source field by Stats Data Aging or Audit Data Aging values.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating