SQL Server Reporting Services

 

ActiveBatch reports for SQL Server requires the SQL Server Reporting Services (SSRS) to be installed and configured. It is recommended the SSRS be on the same version as SQL Server and SSAS. SSRS can be installed on the same machine as SQL Server and SSAS, or on a different machine that can access the SQL Server and SSAS databases. 

 

After installation, initial configuration of SSRS should be done by using the Reporting Services Configuration Manager (RSCM). The RSCM lets you to set up the URLs where the SQL Server reports can be accessed, along with the database where reports and settings are stored and users who can access and execute the reports.  Below is an image of the Reporting Services Configuration Manager.

 

SQL Server Reporting Services (SSRS) Configuration Manager

    

An explanation of the configuration steps are provided below. All steps except for the optional ones should be completed in the given order.

 

Service Account: Provide a built-in or domain account to run the SSRS.

 

Web Service URL: Configure the URL, port, SSL (optional) and virtual directory name. Default URL is http://localhost:80/ReportServer/ 

 

Database: Configure the database server and instance where reports and application data will be stored. (This is different than ActiveBatch’s reporting database.) Make sure that a valid service account is provided to connect to the database server and instance.

 

Report Manager URL: Configure the URL for the management (administration) site for reports.

 

E-mail Settings: Configure an email account to receive emails from SSRS. (optional)

 

Execution Account: Configure a domain account to execute the reports. If an execution account is provided, the report data sources do not require credentials to connect to SQL Server or SSAS. ActiveBatch reports do not need an execution account, since the ActiveBatch Reporting Manager configures the data sources while deploying the reports to SSRS.

 

Encryption Keys: Create a key pair to encrypt sensitive data that is stored in the SSRS database. (optional)

Scale-out Deployment: You can join multiple report servers into one SSRS database. (optional)