Quantcast
Channel: SQL Server High Availability and Disaster Recovery forum
Viewing all articles
Browse latest Browse all 4689

Getting back to Always On again

$
0
0

Hi all of you,

We run an Always On with two Availability Groups, one for transactional ERP databases and another one for Reporting/SharePoint databases.

Let’s focus on Always On Transactional Group, a picture worths a thousand words:

As you can see in the picture, we have primary and secondary nodes as synchronous, being readable both. And, (here is my question) the third one node acting as asynchronous mode.

This third node run Sql Server Analysis Services service is just intended for OLAP and nothing else there.

So far so good but now have got two questions:

1)Why is set up as Manual mode for synchronous nodes? 

2)Because I want to avoid that ERP clients connecting to the listener is consuming or querying in one sense this third node… is correct that third node synchronous be ‘readable’? What does Read-only intent mean?

The third node is in the same Windows Failover Cluster

My concern is setting ‘Read-only intent’ in the third node will leave the databases there in bad state (recovering or something like that)

I don't know if my second questions makes sense or not...

Thanks for share your comments and hints on that!!


Viewing all articles
Browse latest Browse all 4689

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>