Tag Archives: SQL Server mirror

SQL Server Configuration for Skype for Business Server 2015 with SQL Mirror

SQL Server Configuration is a crucial part of the Skype for Business Server deployment. For SQL Server installation you can follow my preceding post Step by step SQL Server Installation for Skype for Business Server 2015. The below configuration mainly focus on settings which are necessary for mirror configuration.

First of all make sure network discovery, file and printer sharing is turned on.

If you are using default instance name then there is no need to setup the TCP Port. As we generally use named instance and by default SQL Server uses “TCP Dynamic Ports” for named instance. We need to specify static port which will be used by the Skype for Business Server to connect.

Open Sql Server Configuration Manager

Go to the SQL Server Network Configuration

Select “Protocols for ‘Instance Name'”

Go to the TCP/IP properties and click in “IP Addresses” tab

Scroll down and select TCP Port.

Assign “1433” and apply the settings.

Go to the SQL Server Services

Restart the SQL server instance service.


Now, open Windows Firewall and go the Advanced Settings.

Create inbound rules as shown below. 7022

If this server is witness server then create one more rule to open port number 7022 which is necessary for witness configuration.

Enable Inbound Firewall rules which are highlighted below in the screenshot.


Now you are done with the configuration part. I hope it worked for you J



Step by step SQL Server Installation for Skype for Business Server 2015

SQL server installation is simple and many IT folks know about it. Still, I am writing this blog post for those people who are not much comfortable with SQL Server. As you know SQL is an important and key server role in Lync & Skype for Business Server. It maintains Skype for Business Back End databases, Archiving and Monitoring databases, and Persistent Chat and Persistent Chat Compliance databases. Installation steps are common across the versions. In this article, I am going to capture installation steps for SQL Server 2014 which will be part of the SQL mirror. This mirror will be used for Skype for Business Back End and Archiving & Monitoring Server databases. As per your requirements and design, you can follow the same steps to create two different mirrors one for Back End databases and another for Archiving & Monitoring databases.

First of all install .Net Framework 3.5 either from GUI or you can use below PowerShell command to install the same. Make sure Windows Server media is connected to sql server, in my case that is connect as H:


Run SQL Server setup from installation media.


Select Installation and click on “New SQL Server stand-alone or add features to an existing installation”


Enter the product key and click on Next.


Accept the license terms and click on Next.


Click on Next.


Ignore this error if you are getting and click on Next.


Click on Next.


Ignore the warning and click on Next.


Select “SQL Server Feature Installation” and click on Next.


For Back End, Archiving, Persistent Chat and Persistent Chat Compliance databases, select the below instance features.

Change the installation path if you want to keep SQL binaries on different location otherwise click on Next.


For Monitoring Server databases, select “Reporting Services – Native” also.


Write the instance name and click on Next.


It is best to use specific service account instead of default.


In Server Configuration tab under “Database Engine Configuration” add users who will have SQL administrative rights.


In Data Directories tab, change the location for databases, log and temp directories as per your design and click on Next.


Use default option and click on Next.


Click on Install.



Once your SQL Server installation is completed. Open SQL Server Studio Manager to cross verify the installation and connectivity.

Use the same installation step for second server. While for witness server either you can install SQL Server express edition or can use any other existing SQL instance.