Different Ways to Monitor SQL Server AlwaysOn Availability Groups

Total: 21 Average: 3.7

In my previous articles, I have explained the step-by-step process of deploying an AlwaysOn Availability group on SQL Server 2017. In this article, I am going to explain how to monitor AlwaysOn availability groups.

First, let’s review the configuration of the availability group we had deployed previously. To do that, open SQL Server Management Studio Expand database engine from the object explorer Expand “AlwaysOn High Availability Expand “Availability Groups.” You can see the availability group named SQLAAG. Under this availability group (SQLAAG), you can see the list of availability replicas, availability databases, and availability group listeners. Read More

SQL Server High availability: Install SQL Server failover clustered instance Part 2

Total: 18 Average: 3.8

In my previous article, I have explained the step-by-step process of installing SQL Server Failover Clustered Instance. In this article, I will explain how to add a secondary node to the existing failover clustered instance.

Install SQL Server Failover Cluster instance

Once SQL Server is installed on an SQL01.dc.Local node, connect to SQL02.dc.Local and run setup.exe – SQL Server installation wizard opens. In the wizard, select “Installation” from the panel on the left and click on “Add node to a SQL Server failover cluster”. See the following image:

Read More

SQL Server AlwaysOn Availability Groups: Installation and configuration, Part 2

Total: 21 Average: 3.9

In my previous article, I have explained the process of installing and creating a failover cluster and how to enable the AlwaysOn availability group.

In this article, I am going to explain the step-by-step deployment process of SQL Server AlwaysOn Availability groups using wizards. The deployment configurations look the following way:

Read More

SQL Server AlwaysOn Availability Groups: Installation and configuration, Part 1

Total: 17 Average: 3.6

In this article, I will explain the process of installing pre-requisites to deploy the SQL Server AlwaysOn availability group.

For the demonstration, I have prepared a demo set up at my work station. See the following components:

Virtual Machine Host Name Purpose
Domain Controller DC.Local The domain controller is installed on this machine
Primary Replica SQL01.DC.Local This machine acts as a Primary replica in the Availability group
Secondary Replica SQL02.DC.Local This machine acts as a Secondary replica in the Availability group. This replica is in a Synchronous commit mode
Secondary Replica with SQL03.DC.Local This machine acts as a secondary replica in the Availability group. This replica is in an Asynchronous commit mode

I will explain the following actions:

  1. Installing a failover clustering role
  2. Create a failover cluster
  3. Enable AlwaysOn availability group features in SQL Server

Read More

How to install SQL Server vNext and Azure data studio on Ubuntu 18.04

Total: 15 Average: 3.4

Azure data studio is a cross-platform database management tool. This tool is used to connect, configure, and administrate SQL Server instances installed locally or in the cloud. This tool can be installed on the following operating systems:

  1. Microsoft Windows
  2. Linux
    • Redgate
    • Debian
    • Ubuntu
  3. macOS

Initially, Microsoft introduced this tool as the “SQL Server operations studio.” Later they renamed it Azure Data Studio. You can get more information about it here.

In this article, I am going to explain the step-by-step installation process of SQL Server 2017 and Azure data studio on Ubuntu. I have divided the article into two parts. Firstly, we will install SQL Server 2017, and later I will explain the process of installing Azure Data Studio. For demonstration purposes, I have created a virtual machine and installed Ubuntu 18.04 on it. You can download Ubuntu here. Read More

Move System Databases in the SQL Server Failover Cluster

Total: 18 Average: 3.4

Recently, I was assigned to a project – our customer purchased a new SAN, and they wanted us to replace the old one with a new SAN. User and system databases utilized SAN, meanwhile, the operating system and SQL were installed on the server’s local disks. Lucky us..!! The idea was to move the existing user and system databases to a new SAN and keep the downtime as minimum as possible. So, to minimize the downtime, instead of reinstalling OS and SQL, we decided to use the following approach.

  1. Attach a new SAN to an existing server, create new drives on it, and add those drives to an existing failover cluster instance.
  2. Stop SQL Server, copy master, model, and msdb databases on new drives and start the SQL services.
  3. Move User databases to new drives and remove the old SAN.

Read More

SQL Server High availability: Add new disk to an existing failover cluster instance

Total: 3 Average: 5

In my previous article, I have explained the step-by-step process of installing a node in existing SQL Server Failover Cluster Instance. Along with that, I have also demonstrated manual failover and automatic failover.

In this article, I am going to demonstrate the process of adding a disk in a failover cluster and then move the existing database to a new drive. Read More