The System Center documentation clearly states you must use a separate instance of Reporting Services for each component of the suite.  Well that’s fine, but you don’t want to have multiple Reporting Services servers just for reporting.  In my series of posts that outline how to install SQL for System Center 2016 (links below), we used a 4 box configuration that you can see in the diagram below.  In this article we will install another instance of Reporting Services on the two Reporting Services servers.  The same process can be used if you are using Reporting Services collocated on the SQL Servers.

best site to order clomid Installing SQL for System Center 2016 Posts

Part 1 – Installing Highly Available SQL 2016 with SP1 for System Center 2016 – Part 1 (SQL Server AlwaysOn Availability Groups)
Part 2 – Installing Highly Available SQL 2016 with SP1 for System Center 2016 – Part 2 (Network Load Balancing Reporting Services)
Part 3 – Installing Highly Available SQL 2016 with SP1 for System Center 2016 – Part 3 (Reporting Services on a SQL Cluster)

can you buy viagra in america

Diagram of Setup

image

Installing a new Reporting Services Instances

You can install multiple instances of Microsoft SQL Server Reporting Services on the same computer. Each instance will have its own report server database, configuration files, and virtual directories. One instance can be the default instance. All other instances must be named instances. A server can run multiple instances of Reporting Services at the same time, and each instance runs independently of the other instances.

Install an additional Reporting Services instance on the computer that is running Reporting Services. To install additional instances, you must run the SQL Server Setup Wizard one time for each report server instance that you want to install. You cannot install multiple instances at the same time.

When you install multiple report server instances on the same computer, each additional instance must be installed as a named instance. To install an additional, named instance, you must run the SQL Server Setup Wizard again.

Insert the SQL Server Media and run buy Lyrica from canada setup.exe

Click Install and then click New SQL Server stand-alone installation or add features to an existing installation

image_thumb2_thumb

Select Microsoft Update if you wish and click Next

image_thumb5_thumb

Continue through the wizard until you reach the Installation Type screen and ensure Perform a new installation of SQL Server 2016 is selected and click Next

image

Enter your Product Key or click Specify a free edition for a 180 free trial

image_thumb3_thumb

Click I accept the licence terms and click Next

image_thumb4_thumb

Select Reporting Services – Native and click Next

image

Enter a name for the Reporting instance and click Next

image

Enter your SQL Service Account credential and click Next

image

On the Configuration screen you will see we have no option than to Install only.  Therefore, click Next

image_thumb26

Click Install

image_thumb27

Once setup is complete click Close

image_thumb28

Now do exactly the same process on the second Report Server if you have a HA deployment.

 

Configuring the second SQL Server 2016 Reporting Services instance

From the Start Menu open the Reporting Services Configuration Manager

On the Connection Screen select the new Reporting Services Instance and Click Connect

image

Click Web Service URL then click Apply to accept the defaults

image

You should see success in the Results pane

image_thumb31

Now click on Database then click Change Database

image_thumb32

Click Create a new report server database and click Next

image_thumb33

Enter the name of your AlwaysOn Availability group LISTENER or SQL Server if you have just one and click Test Connection and ensure it succeeds.  Then click Next

image_thumb34

The default name is ReportServer but as this is a second instance that name will be taken so change it to something relevant and click Next

image

Accept the defaults for the credentials and click Next

image_thumb36

On the Summary click Next

Once the wizard has ran and everything was successful click Finish

image_thumb37

Click the Web Portal URL link. Accept all the default values and click Apply

image

Verify that the reporting services instance is configured and working properly. You can do this by opening a web browser and accessing the URL defined in the Web Portal URL page

image

 

Now we have a second instance of  SQL Server 2016 Reporting Services working for the first node we need to add the second node if you have one.

 

Configuring the second SQL Server 2016 Reporting Services Server

Log onto the second Reporting Services / SQL server.

From the Start Menu open the Reporting Services Configuration Manager

On the Connection Screen select the new Reporting Services Instance and Click Connect

image

Click Web Service URL then click Apply to accept the defaults

image

You should see success in the Results pane

image_thumb31

Do the same on the Web Portal URL.

Click the Database link and click the Change Database button. This will open the Report Server Database Configuration Wizard

image_thumb40

Select the Choose an existing report server database option and click Next

image_thumb41

Enter the name of your AlwaysOn Availability group LISTENER or SQL Server and click Test Connection and ensure it succeeds.  Then click Next

image_thumb42

Select your new ReportServer instance database from the drop down menu and click Next

image

Accept the defaults for the credentials and click Next

image_thumb44

On the Summary click Next

Once the wizard has ran and everything was successful click Finish

image_thumb46

 

Join the second SQL Server 2016 Reporting Services instance to the Scale-Out Deployment

In the past, you may not have paid attention to the last link in the Reporting Services Configuration Manager – the Scale-Out Deployment link. When you click on that link, you should see a message stating that you should connect to the report server that has already been joined to this scale-out deployment.

Click Scale-out Deployment

When you click on that link, you should see a message stating that you should connect to the report server that has already been joined to this scale-out deployment

image_thumb47

 

This means that we need to connect to the first Reporting Services Server that we configured and accept the second reporting services instance to join the scale-out deployment.

On the first Reporting Services Server in Reporting Services Configuration Manager click Add Server

image

The server should now successfully of joined the web farm

image

Go back to the second Reporting Services Server and Click the Web Portal URL link. Accept all the default values and click Apply

Now test to ensure you can navigate to the Web Portal URL

image

 

 

Encyption Keys

We now need to ensure that the encryption key from the first node is restored on the second node to be able to share encrypted data between the two.

On the Report Server Configuration Manager click Encryption Keys.  Click Backup and save it on your network that can be access by the second Reporting Services Server.

image_thumb51

Now restore the key on the second Reporting Services Server

 

Final Test

Now the installation and configuration is all complete, all that there is left to do is to test the Load Balanced URL.  Navigate to http://loadbalanceddnsname/Reports

image_thumb52

 

Adding DB’s to the AlwaysOn Cluster

One thing the wizards don’t do is add the Databases to the cluster therefore lets do this.

Open SQL Management Studio on the first SQL server and expand Databases.  Right click the new reporting instance database and click Properties and select Options and ensure the Recovery model is set to Full.

image_thumb1

Closer the properties window and right click the new reporting instance database Tasks > Backup

Click Add and specify the backup location then click OK

image_thumb2

Right click the Availability Group and click Add Database

image_thumb3

Once the wizard opens click Next on the Introduction screen and On the Select Databases screen select the ReportServer which should state “Meets prerequisites” then click Next

image

On the Select Initial Data Synchronization step enter a File Share location on your network and click Next

On the Connect to Existing Secondary Replicas step click Connect and connect to the secondary SQL Server and click Next

Ensure the validation passes and click Next

image_thumb5

Then click Finish and the ReportServer database should now be added to the AlwaysOn Availability group

image

Now do the same with the ReportServerTempDB

That’s it, you now have a second Reporting Services instance for one of your System Center components.