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

MessageStats 7.8 - 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.

To address slow running reports, you can:

Reduce the number of parts in an At A Glance report or in a custom report.

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 .

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:

Database Management

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.

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

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.

評価を選択