With SQL Server 2012 Microsoft introduced the AlwaysOn Availability Group feature, and since then many changes and improvements have been made. This article is an update to another article, and will cover the prerequisites and steps for installing AlwaysOn in your SQL Server 2019 environment. Prerequisites Before implementing your AlwaysOn Availability Group (AG), make sure […]
2025-11-25
92 reads
Knowing the usage from all workloads is definitely better than focusing on only the primary or a single secondary. But what if I want to make more informed decisions, incorporating row counts, size, and index columns into this output?
2025-10-27
Spotting synchronization disconnects between a primary and a secondary data center in a distributed availability group configuration can be hard, so here are valuable tools to help you with it
2025-10-10
1,087 reads
Synchronous replicas in SQL Server Availability Groups promise no data loss, but they don’t promise zero delay; under heavy load they can still fall behind. This article shows how to measure and track that hidden replication delay using SQL Server performance counters, so you can see how well your system keeps up during IO‑intensive operations and plan maintenance more safely.
2025-09-17
SQL Server 2022 introduced a new feature called Contained Availability Groups. It allows the Database Administrators to effectively manage the Server Level objects, such as Logins, SQL Agent jobs, etc. in an HA environment. In today's article, we will learn about this new feature of SQL Server. The Challenge of Managing Server Objects in Availability […]
2025-08-20
8,674 reads
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
This article describes the process to create a read-scale cross-platform SQL Server Availability Group where the primary is Linux and the secondary is Windows.
2025-07-23
368 reads
This article shows the final step of an availability group creation, specifically for a distributed clusterless one.
2025-07-14
4,204 reads
2025-05-05
445 reads
2025-02-10
444 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,...
Comments posted to this topic are about the item The AI Bubble and the...
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...
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