How to use SQL Server Always on technology

Using SQL Server Always on technology, if the configuration is the default configuration, there will be a high primary server CPU, such as the default configuration is as follows:

Customization is needed to solve this problem.

Let's take a look at the meaning of these options in the above figure

Connections in the main role

Allow all connections

Primary instance allows all connections (such as read/write/admin) if the current server is the primary role

Allow read/write connections

If the current server is the primary role, primary instance only allow read/write connections (if the connection is through SSMS, the error will be an error, and SQLCMD is also a report)

Readable auxiliary Copy

Is

If the current server is a primary role, all secondary servers are visible (through SSMs can look at the structure, data, but not change)

Read Only Intent

If the current server is the primary role, all secondary servers only allow read connections (you need to add a key when establishing a connection to indicate a read-only connection: applicationintent=readonly)

Whether

If the current server is the primary role, all secondary servers can not see (through the SSMs can connect, but can't see, will error, such as the following)