サポートと今すぐチャット
サポートとのチャット

MessageStats 7.8.1 - Administrator Guide

What is MessageStats? MessageStats Information Sources Using the Console Interface Creating a Connection to Exchange Creating Gathering Tasks Default Gatherings Extending Gathering Tasks Configuring Audits Setting MessageStats Server Properties Setting Configuration Properties Setting Exchange Organization Properties Setting Exchange Server Properties Setting Task Execution Server Properties Setting Task Default Properties Compressing Tracking Log Files Using the MessageStats Reports Console Database Management Appendix A:Microsoft ASP.NET Configuration Issues Appendix B: Gathering Task Dependencies Appendix C:Troubleshooting Permission Problems

Performance Considerations for MessageStats Reports

MessageStats Reports are optimized for performance for a number of standard usage scenarios and date periods. Due to the volume of data in the MessageStats Database and complexity of reports, report performance can be slower in some scenarios.

Improving Report Rendering Performance

To address slow running reports, you can:

•
Reduce the number of parts in an At A Glance report or in a custom report.
•
Increase report rendering efficiency by specifying shorter date ranges or time periods.
Performing Regular Database Maintenance

You can ensure that reports run quickly by performing routine maintenance on the MessageStats database including reindexing and defragmenting the database. For information about reindexing and defragmenting data, see Using Database Management .

Creating Subscriptions Using Alternate Delivery Methods

When report consumers require long running and complex reports, you might consider creating report subscriptions that use a delivery method other than Send as Link, thereby allowing MessageStats Reports to process the report offline for delivery to a web site or within an email body. For information about report subscriptions, see the MessageStats Reports User Guide.

Best Practices for Report Performance

To ensure optimal performance, it is recommended that you consider the following options:

•
Install MessageStats Reports on a separate computer to avoid impacts to memory and CPU usage due to report rendering.
•
Set initial filter options to reduce the data set queries. Select specific filter options or a specific date range to ensure that a smaller result set is searched, resulting in quicker results.
•
For audits, ensure that you carefully define the mailboxes, Internet domains, message subjects, and message delivery times. Extensive audit information in the MessageStats Database can slow performance since the report queries must scan a larger dataset to produce audit reports. For information about auditing, see About Audits .
•
Run statistical reports at the same frequency as the gathering recurrence for the report content. For example, if you configure MessageStats to collect distribution group information on the first day of each month but you create a report subscription for distribution groups to be sent every Friday, only the first Friday of the month contains new information. Each subsequent Friday of the month the report does not contain any new information.
•
Create subscriptions only for reports that are useful to oversee the operation of your Exchange organizations. For example, set subscriptions for summary reports to identify anomalies and trends. Based on the summary reports, you can create additional reports to investigate any unexpected results.
•
Select the report that best that best suits your needs. Several reports may include the same data organized in different ways (such as Top Senders by Messages and Top Senders by Volume). Determine if one report satisfies the reporting need instead of duplicating the effort.

Database Management

•
About the MessageStats Database
•
Managing your MessageStats Database
•
Using Database Management
•
Deleting Historical Data
•
Database Maintenance— Reindexing and Defragmenting the Database
•
Deleting Object or Report Data
•
Clearing the Database

About the MessageStats Database

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

When you install MessageStats, 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. For more information, For more information, see Configuring the MessageStats Server.

It is recommended that you adhere to Microsoft best practices and create regular backups of your database.

Supported Database Implementations

The supported database server implementations that you can use to store tracking log and Exchange object data are as follows:

•
SQL Server 2012
•
SQL Server 2014
•
SQL Server 2016
•
SQL Server 2017
•
SQL Server 2019
•
SQL Server 2022

SQL Server Express is supported for evaluation scenarios only. SQL Server Agent must be installed and running to use the Database Management tasks such as database reindexing, defragmenting, or database aging. Since SQL Express does not include the SQL Server Agent, the Database Management tasks are not available when running on SQL Express.

関連ドキュメント

The document was helpful.

評価を選択

I easily found the information I needed.

評価を選択