Microsoft announced cross-platform support of SQL Server – the SQL Server 2017 and SQL Server 2019 work on Microsoft Windows and Linux. We can install SQL Server 2017 and higher on Red Hat Enterprise Linux, Ubuntu, and SUSE Enterprise Server. We can also set up high availability and disaster recovery mechanism for SQL Server on Linux like SQL Server Log shipping and AlwaysOn Availability Group.Read More
This article explains the step by step deployment process of the SQL Server Log shipping. It is the database-level disaster recovery solution that is easy to set up and maintain.
The log shipping involves three steps:
- Generate the log backup on the primary database.
- Copy the backup to the network location or the specific directory on the secondary server.
- Restore the log backup on the secondary server.
The log shipping technology performs the steps described above by using SQL Server agent jobs. During the configuration process, the log shipping wizard creates those jobs on primary and secondary servers.Read More
SQL Server Agent is a component used for the database tasks automation. For instance, we need to perform Index maintenance on Production servers during the non-business hours only. So, we create a SQL Server job of running index maintenance and schedule it for “off” hours.
When we install SQL Server, the SQL Server Agent service is disabled. First, we enable it and start it manually. Then, we configure the SQL Server job, using SQL Server Management Studio and the system stored procedures of the MSDB database.
This article explains how to create a SQL Server Job using the system stored procedures of the MSDB database.Read More
Database mirroring is a SQL Server high availability solution provided by Microsoft, with the following components.
- Principal database server: a source database that you configure for the mirroring.
- Mirror database server: a destination database that you must restore with NORECOVERY. Ideally, a mirrored database should be on a separate server.
- Witness Server: an optional component that you can set up to configure the mirror with automatic failover.
- Endpoint: the communication medium used by the principal and mirror server. The mirror listens on port number 5022; however, you can change it during the configuration.
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
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:
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:
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:
- Installing a failover clustering role
- Create a failover cluster
- Enable AlwaysOn availability group features in SQL Server
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:
- Microsoft Windows
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