All About SQL

Blog Post

How/Why/What is DevOps?

Thanks to Grant for hosting this month’s T-SQL Tuesday found (http://www.scarydba.com/2017/06/06/t-sql-tuesday-091-databases-devops/) where it is a chance to share our DevOps...

2017-06-13

552 reads

Blogs

9 questions to ask before adding generative AI to your data project

By

Will adding generative AI to your data project improve the outcomes? It might, but...

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...

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...

Migrate from Linux to Windows with Availability Groups

By Pablo Echeverria

Comments posted to this topic are about the item Migrate from Linux to Windows...

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...

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