A customer has a database that is already set up in a SQL Server Availability Group. Since this database hosts sensitive data, there is a need to encrypt the primary and all secondary replicas of the data. In this article, we will walk through how this can be done.
2025-08-13
Introduction Sometimes we face the scenario in an enterprise environment that the database in SQL Server Always On Availability Group (AOAG) has high concurrency read and write access from application servers. If we keep using the one network interface card for both network traffic of database connections from application servers and database mirroring between AOAG […]
2025-09-01 (first published: 2023-05-08)
5,941 reads
This script will create the necessary login and linked servers on a given availability replica. Please ensure that the script is executed on all the replicas.
2022-02-22 (first published: 2022-01-25)
7,781 reads
2022-01-19
368 reads
2022-01-12
361 reads
This guide helps you get started on troubleshooting some of the common issues in AlwaysOn Availability Groups and monitoring AlwaysOn Availability Groups. It is intended to provide original content as well as a landing page of useful information that is already published elsewhere.
2024-01-09 (first published: 2021-08-25)
Availability databases hosted on SQL Server Always On Availability Groups (AG) can be connected using a unique Virtual Network Name (VNN), called the Availability Group Listener. When an Availability Group is enabled, clients can connect to databases in both primary and secondary replicas without explicitly specifying the SQL Server instance name. You don’t even need […]
2021-05-17
9,543 reads
In this article, we will review how to configure Always On Availability Groups in Ubuntu Server using the Pacemaker cluster. The following are the high-level steps to configure Always On Availability Groups (AOAG) with an Ubuntu server. Install SQL Server on Ubuntu 16.04 Install Pacemaker agents and configure the cluster Create Always On Availability Groups Create […]
2020-08-25
3,574 reads
This script can be used to generate Dashboard report for Always-on AG databases. Script can be placed in SQL Agent to generate report.
2020-05-22 (first published: 2020-05-12)
3,111 reads
Availability databases hosted on SQL Server Always On Availability Groups (AG) can be connected using a unique Virtual Network Name (VNN), called the Availability Group Listener. When an Availability Group is enabled, clients can connect to databases in both primary and secondary replicas without explicitly specifying the SQL Server instance name. You don’t even need […]
2019-07-02
136,851 reads
By Steve Jones
Superheroes and saints never make art. Only imperfect beings can make art because art...
One feature that I have been waiting for years! The new announcement around optimize...
Following on from my last post about Getting Started With KubeVirt & SQL Server,...
Hi, in a simple oledb source->derived column->oledb destination data flow, 2 of my...
hi, i noticed the sqlhealth extended event is on by default , and it...
Using New-AzSqlInstanceServerTrustCertificate to import a certificate and get the message New-AzSqlInstanceServerTrustCertificate: Long running operation...
I am currently working with Sql Server 2022 and AdventureWorks database. First of all, let's set the "Read Committed Snapshot" to ON:
use master; go alter database AdventureWorks set read_committed_snapshot on with no_wait; goThen, from Session 1, I execute the following code:
--Session 1 use AdventureWorks; go create table ##t1 (id int, f1 varchar(10)); go insert into ##t1 values (1, 'A');From another session, called Session 2, I open a transaction and execute the following update:
--Session 2 use AdventureWorks; go begin tran; update ##t1 set f1 = 'B' where id = 1;Now, going back to Session 1, what happens if I execute this statement?
--Session 1 select f1 from ##t1 where id = 1;See possible answers