August 15, 2018 at 5:50 am
I would add make sure you test this fully before going live, because long-running reports run against a readable secondary can block the redo thread of database in a "synchronous" AG, causing it to stop being synchronous.
This could also cause your transaction log on the read/write replica to grow because it can't be truncated due to this issue.
August 15, 2018 at 7:21 am
other choice was an active passive cluster with AG for the read only node. interested in how many people have tried that approach
August 15, 2018 at 12:49 pm
tcronin 95651 - Wednesday, August 15, 2018 7:21 AMother choice was an active passive cluster with AG for the read only node. interested in how many people have tried that approach
I have this setup - but all nodes in the same data center. It works quite well as long as the readable secondary has no quorum votes and is not synchronous. No need for a listener in this configuration either - as all report users will access the secondary directly.
Jeffrey Williams
“We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”
― Charles R. Swindoll
How to post questions to get better answers faster
Managing Transaction Logs
August 19, 2018 at 7:49 am
Beatrix Kiddo - Wednesday, August 15, 2018 5:50 AMI would add make sure you test this fully before going live, because long-running reports run against a readable secondary can block the redo thread of database in a "synchronous" AG, causing it to stop being synchronous.This could also cause your transaction log on the read/write replica to grow because it can't be truncated due to this issue.
+1 I've ran into this myself.
Viewing 4 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply