October 2, 2023 at 4:33 pm
I hate to possibly jinx myself, but I've had 5 failovers with no secondaries out of sync. I've turned on ADR for a bunch of my databases. Maybe about 60 of the largest ones (out of 185), only 60 because you have to have exclusive access to turn it on. I'm on the latest patch but I think it is more the ADR helping. I first did 10 and I had less secondaries out of sync so I continued enabling it for more databases. I believe with ADR it is doing less work at startup and requiring less threads.
October 12, 2023 at 8:46 pm
We just pushed CU22 and are still experiencing the problem. We had 3 dbs that stopped synchronizing even after doubling CPU and RAM per Microsoft recommendations. We are uploading logs to Microsoft for review, hopefully they'll find something useful but I'm not holding my breath.
ROTHJ: Thanks for the input, I'll ask my team and MS if we might be a good candidate to try ADR (although I'd hope that if we were they would have recommended it by now, we've had a case open for 6 months!)
October 12, 2023 at 8:52 pm
I'm now up to 10 failovers with no sync issues. I'm also on CU22.
October 13, 2023 at 12:27 pm
I see they just released CU23 but I don't see any mention of a fix for this issue.
February 20, 2024 at 5:30 pm
Closing the loop here- After almost a year of mostly unproductive back-and-forth on a MS ticket, we finally got the straight answer we suspected (paraphrasing MS response )
We are now working on a costly database-combining project to drive down our overall database count.
February 21, 2024 at 1:32 pm
I stopped by just to gasp about 300 dbs/server and 50 dbs/ag. I think I legit stopped breathing for just a second.
Viewing 6 posts - 31 through 36 (of 36 total)
You must be logged in to reply to this topic. Login to reply