Availability Group (AG)

SQLServerCentral Article

Basic Always On Availability Groups in SQL Server Standard

  • Article

Once Windows Server Failover Clusters have been set up, we can set up Availability Groups in SQL Server. This article will focus on setting up Basic Always-On Availability Groups in SQL Server Standard Edition.
This facilitates High Availability in SQL Server Standard, with three levels of availability and failover:
Asynchronous commit with manual or forced failover,
Synchronous commit with manual or forced failover,
Synchronous commit with automatic failover.

★ ★ ★ ★ ★ ★ ★ ★ ★ ★

(3)

You rated this post out of 5. Change rating

2024-06-05

12,318 reads

SQLServerCentral Article

Add a Second NIC for an Availability Group to Separate Network Traffic

  • Article

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 […]

★ ★ ★ ★ ★ ★ ★ ★ ★ ★

(5)

You rated this post out of 5. Change rating

2025-09-01 (first published: )

5,941 reads

Blogs

Advice I Like: Art

By

Superheroes and saints never make art. Only imperfect beings can make art because art...

Why Optimize CPU for RDS SQL Server is a game changer

By

One feature that I have been waiting for years! The new announcement around optimize...

Performance tuning KubeVirt for SQL Server

By

Following on from my last post about Getting Started With KubeVirt & SQL Server,...

Read the latest Blogs

Forums

The AI Bubble and the Weak Foundation Beam

By dbakevlar

Comments posted to this topic are about the item The AI Bubble and the...

data type gets lost in data flow

By stan

Hi, in a simple oledb source->derived column->oledb destination    data flow, 2 of my...

i noticed the sqlhealth extende event is on by default , so can i reduce

By rajemessage 14195

hi, i noticed the sqlhealth extended event is on by default , and it...

Visit the forum

Question of the Day

The Read Committed Snapshot Isolation behaviour

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;
go
Then, 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