Chat now with support
与支持团队交流

Enterprise Reporter 3.2.1 - Installation and Deployment Guide

Product Overview Installation Considerations for Enterprise Reporter Installing and Configuring Enterprise Reporter Managing Your Enterprise Reporter Deployment Troubleshooting Issues with Enterprise Reporter Appendix: Database Content Wizard Appendix: Encryption Key Manager Appendix: Log Viewer

Performing Database Maintenance

Using the Perform Database Maintenance option, you can perform consistency checks, reset identity columns, or rebuild indexes.

2
On the computer hosting the Enterprise Reporter server, click the Start menu and select All Programs|Quest|Enterprise Reporter|Database Wizard.
3
Click Next.
4
Choose Perform Database Maintenance, and click Next.
5
7
Click Next.
9
Click Finish to complete the request and close the wizard.

 

Managing Your Enterprise Reporter Deployment

Optimizing Enterprise Reporter

Enterprise Reporter is very scalable. Properly planning and managing the system is important to ensure that your data is collected as quickly and effectively as possible. There are many ways to improve the performance of your deployment.

See also:

Enterprise Reporter Server and Database Considerations

You need to choose a host computer for Enterprise Reporter server and a SQL Server® to host the Enterprise Reporter database. Your decision will affect the performance of the product.

The Enterprise Reporter server communicates directly with the database frequently. Locate the Enterprise Reporter server physically close to the SQL Server® for best results.

The nodes also regularly connect to the database. The more nodes you have in your deployment, and the more discoveries you run, the greater the impact on the SQL Server®. Choose a SQL Server® with enough power to manage the connections and data transfer from the nodes. Check your Microsoft® SQL Server® documentation for more information on system requirements.

Enterprise Reporter supports a variety of SQL configurations. You can use a regular SQL instance, a SQL cluster, or a mirrored database. If your SQL deployment supports it, using clusters or mirrors allows for automatic failover recovery in the event that a SQL Server® is down.

See also:

相关文档