Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Performance impact of Reporting Services

Created: 20 Aug 2013 • Updated: 25 Oct 2013 | 4 comments
sujith.poojari's picture
This issue has been solved. See solution.

We have a single EV server for Exchange Archiving for 550 Users. The SQL server is installed in the same box. Please find the hardware/software configuration as follows:

EV: 10.0.0 (Planning to upgrade to 10.0.4)

Windows: 2008 R2 SP1

SQL Server 2008 R2 Enterprise with Reporting

CPU: Intel Xeon E5-2620 2 Cores

RAM: 16 GB

We are planning to install Reporting Services for all EV databases.

I would like to know if there would be any performance impact if reporting is configured on the same machine.

Do we need to install reporting on a seperate machine?

Operating Systems:

Comments 4 CommentsJump to latest comment

A_J's picture

Hi Sujith,

Typically, the Enterprise Vault Reporting component is installed without any other Enterprise Vault components on a server that runs Microsoft SQL Server Reporting Services.
 
But if the environment growth is restricted then you can install it on EV Server.
 
If not then it is recommended to install it on a separate server.
 
 
To know more about the pre-requisites you can check the Installing and configuring Guide for enterprise Vault..
 
 
I hope this helps...
EdLacey's picture

If you are not seeing any performance issues running EV & SQL on the same servers at the moment then you won't have an issue installing and running EV Reporting services. To make life simpler you could install Reporting services during your upgrade to 10.0.4.

A_J's picture

Hi Sujith,

Let me know if you have any further queries...

GabeV's picture

Hi Sujith,

Running EV 10.0.4 and SQL on the same box is not a good idea. Perhaps for testing purposes would be OK, but not for production. Just for EV 10.0.4, the minimum memory requirement is 16GB of RAM and for SQL (according with Miccrosoft) 2GB or more is recommended.

For instance, the EV indexing service for EV 10, by design, uses 1.5 times the total memory of your Windows box. Thus, you might have a performance issue with EV indexing with that configuration. I'd recommend you to separate EV and SQL and then you can (1) install a third server with SQL reporting services or (2) install SQL reporting services on the same SQL server and increase the memory to 8GB or more, since for SQL you need at least 2GB for the SQL server core and 4GB for reporting Services:

http://technet.microsoft.com/en-us/library/ms14350...

I hope this helps.

“Success is not final, failure is not fatal: it is the courage to continue that counts.”–Winston Churchill

SOLUTION