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

Enterprise Reporter 3.5.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.

Before performing database maintenance
•
Disable clusters to stop discoveries from being sent to the nodes.
•
Cancel any jobs running on the nodes to stop data from writing to the Enterprise Reporter database.
•
Cancel any report jobs running or scheduled to prevent Report Manager from using the database.
•
Create a backup of the database.
* 
CAUTION: It is strongly recommended that you back up your database. You can restore the backup if there are issues with the upgrade.
•
Stop the Quest Enterprise Reporter Server service.
•
Close the Configuration Manager and Report Manager on all computers.
To perform database maintenance
* 
CAUTION: It is recommended that you backup your Enterprise Reporter database before beginning this process. You cannot undo this operation once it has started.
1
Complete all steps in the procedure Before performing database maintenance .
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.
The Establish Connection page is populated with your existing database and server.
5
If desired, change the SQL Server or database name.
6
If desired, change the authentication type, and provide a user name and password if necessary.
7
Click Next.
8
Select the database maintenance options to perform, and click Next.
9
Click Finish to complete the request and close the wizard.

 

Managing Your Enterprise Reporter Deployment

•
Optimizing Enterprise Reporter
•
Enterprise Reporter server and database considerations
•
Cluster Deployment Considerations
•
Discovery Considerations

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
•
Cluster Deployment Considerations
•
Discovery Considerations

Enterprise Reporter server and database considerations

You must choose a host computer for Enterprise Reporter server and a SQL Server to host the Enterprise Reporter database. Your decision affects the performance of the product.

The Enterprise Reporter server communicates directly with the database frequently. For best results, locate the Enterprise Reporter server physically close to the SQL Server.

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:

•
Failover recovery using SQL clusters
関連ドキュメント

The document was helpful.

評価を選択

I easily found the information I needed.

評価を選択