Enterprise Reporter 3.2.2 - Installation and Deployment Guide

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.

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.

Failover Recovery using SQL Clusters

Using a SQL cluster instead of a single server allows for automatic failover recovery in the event that a SQL Server® is down. Tasks are automatically passed to another SQL Server®. Your cluster can be configured with Always On.