Installing SQL Server with Reporting Services
Topic Last Modified: 2012-10-14
Monitoring Server requires the Microsoft SQL Server database software to store the collected Quality of Experience (QoE) and call detail recording (CDR) data. Monitoring Server describes this data using a standard set of reports that are published by SQL Server Reporting Services. To view the reports, you must also install an instance of SQL Server Reporting Services.
You must install Microsoft SQL Server on the computer that hosts the Monitoring Server database. This can be the same computer that runs Monitoring Server, or it can be a dedicated database server.
Microsoft SQL Server 2005, Microsoft SQL Server 2008, and Microsoft SQL Server 2008 R2 have specific requirements when installing and deploying Microsoft Lync Server 2010 Reporting Services. Because Windows and SQL Server define their security differently, logging on as an administrator in the Active Directory domain does not implicitly grant user rights or permissions for SQL Server. You must also be a member of the sysadmin entity on the SQL Server-based server that you are configuring.
Lync Server 2010 supports the following 64-bit versions of SQL Server:
SQL Server 2008 R2 Enterprise
SQL Server 2008 R2 Standard
SQL Server 2008 Enterprise with Service Pack 1 (SP1) (required) or latest service pack (recommended)
SQL Server 2008 Standard with SP1 (required) or latest service pack (recommended)
SQL Server 2005 Standard Edition with Service Pack 3 (SP3) (required) or latest service pack (recommended)
SQL Server 2005 Enterprise Edition with SP3 (required) or latest service pack (recommended)
Note
SQL Server 2008 Express, SQL Server 2008 R2 Express, and SQL Server 2005 Express Edition are not supported.
You should install the version of SQL Server Reporting Services that matches the version of SQL Server that you have installed. For details about SQL Server, see the SQL Server TechCenter at https://go.microsoft.com/fwlink/p/?LinkId=129045. For details about SQL Server Reporting Services, see "Considerations for Installing Reporting Services" at https://go.microsoft.com/fwlink/p/?LinkID=131042.
If you do not configure the Report Server while installing the Reporting Services, you need to use the Reporting Services Configuration tool to configure the options that are required to run the Report Server after installation is complete.
For details, see "Reporting Services Configuration Tool" at https://go.microsoft.com/fwlink/p/?LinkId=204090 and "Reporting Services Configuration How-to Topics" at https://go.microsoft.com/fwlink/p/?LinkId=187488.
Verifying the Web Service URLs
After you deploy Reporting Services, you need to verify that the Reporting Services Web service URLs, which are used to view the Monitoring Reports, are working correctly. You can choose to use either http or https to deploy reports. If both are available, Reporting Services are installed to https by default.
For details, see "How to: Verify a Reporting Services Installation" at https://go.microsoft.com/fwlink/p/?LinkId=187490.
To verify if the URLs work
Open Reporting Services Configuration Manager from the SQL Server Configuration Tools.
Connect to your instance of Reporting Server.
On the Web Services URL page, click the URLS listed under Report Server Web Service URLs to verify that the link can be opened.
Deploy Monitoring reports to this link by following the steps described in Deploying Monitoring Server Reports.