@chuckboycejr

Blog Post

the game

So things are messed up. Bad. I mean, you lost a $2.7 Billion Dollar Secret Blimp or your team accidentally sent...

2015-10-30

1,067 reads

Blogs

Accelerating Database Modernization Through DevOps & Cloud Integration

By

In today’s enterprise landscape, agility and reliability go hand-in-hand. As organizations modernize legacy infrastructure...

Speaking at the PASS Data Community Summit

By

I’m honored to be speaking at the PASS Data Community Summit in Seattle this...

Article: SQL Server Sample Databases

By

herefore, from Northwind and pubs to WideWorldImporters, I've compiled where to get those databases...

Read the latest Blogs

Forums

How a Legacy Logic Choked SQL Server in a 30-Year-Old Factory

By Chandan Shukla

Comments posted to this topic are about the item How a Legacy Logic Choked...

We Gave Memory-Optimized Tables a Hash Lookup — Then Tried Pattern Matching Instead

By Chandan Shukla

Comments posted to this topic are about the item We Gave Memory-Optimized Tables a...

Always On AG Latency for Read-Only Workload After Failover?

By dbakevlar

Comments posted to this topic are about the item Always On AG Latency for...

Visit the forum

Question of the Day

Always On AG Latency for Read-Only Workload After Failover?

You're responsible for managing a SQL Server environment using Always On Availability Groups across two data centers. During a recent planned failover to the secondary replica, you noticed increased application latency and errors related to read-only routing. Upon investigation, you discover that read-only routing continues pointing to the former primary, now a secondary, for a period of time after the failover.
Which of the following best explains this behavior and how to resolve it?

See possible answers