2023-03-29
357 reads
Availability Group (AG)
How to Use PowerShell to Track a Network Latency Issue in an Always On Availability Group
This article tracks down a problem with Availability Groups due to network bandwidth.
2022-10-21 (first published: 2022-08-09)
5,201 reads
Always On Availability Groups Troubleshooting and Monitoring Guide
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)
A Step by Step Guide to the Availability Group (AG) Listener
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
2021-02-09
1,069 reads
Do *not* place TEMPDB on a local disk in a SQL failover cluster
What happens with tempdb on a local disk in a cluster? Read on to see that you will not get a failover if the local disk fails
2021-01-04
10,049 reads
Steps for Installing AlwaysOn Availability Groups - SQL 2019
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 […]
2020-12-07
151,265 reads
2020-11-16
619 reads
2020-10-22
9,287 reads
2020-10-15
451 reads
Blogs
Advice I Like: Art
By Steve Jones
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
One feature that I have been waiting for years! The new announcement around optimize...
Performance tuning KubeVirt for SQL Server
Following on from my last post about Getting Started With KubeVirt & SQL Server,...
Forums
The AI Bubble and the Weak Foundation Beam
Comments posted to this topic are about the item The AI Bubble and the...
data type gets lost in data flow
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
hi, i noticed the sqlhealth extended event is on by default , and it...
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; 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