Skip to content

Commit fdeeb39

Browse files
GitHubber17GitHubber17
authored
Merge pull request #6790 from MashaMSFT/20180809_agssms
added latency report info to ag section (vsts 1165474)
2 parents e7276e0 + bb07189 commit fdeeb39

1 file changed

Lines changed: 57 additions & 76 deletions

File tree

‎docs/database-engine/availability-groups/windows/use-the-always-on-dashboard-sql-server-management-studio.md‎

Lines changed: 57 additions & 76 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
2-
title: "Use the Always On availability group dashboard (SQL Server Management Studio) | Microsoft Docs"
2+
title: "Use the Always On Availability Group dashboard (SQL Server Management Studio) | Microsoft Docs"
33
ms.custom: ""
4-
ms.date: "10/30/2017"
4+
ms.date: "08/09/2018"
55
ms.prod: sql
66
ms.reviewer: ""
77
ms.suite: "sql"
@@ -19,52 +19,41 @@ author: MashaMSFT
1919
ms.author: mathoma
2020
manager: craigg
2121
---
22-
# Use the Always On availability group dashboard (SQL Server Management Studio)
22+
# Use the Always On Availability Group dashboard (SQL Server Management Studio)
2323
[!INCLUDE[appliesto-ss-xxxx-xxxx-xxx-md](../../../includes/appliesto-ss-xxxx-xxxx-xxx-md.md)]
2424

25-
Database administrators use the Always On availability group dashboard to obtain an at-a-glance view the health of an availability group and its availability replicas and databases in [!INCLUDE[ssCurrent](../../../includes/sscurrent-md.md)]. Some of the typical uses for the availability group d dashboard are:
26-
27-
- Choosing a replica for a manual failover.
25+
Database administrators use the Always On Availability Group dashboard to obtain an at-a-glance view the health of an availability group and its availability replicas and databases in [!INCLUDE[ssCurrent](../../../includes/sscurrent-md.md)]. Some of the typical uses for the availability group dashboard are:
2826

27+
- Choosing a replica for a manual failover.
2928
- Estimating data loss if you force failover.
30-
31-
- Evaluating data-synchronization performance.
32-
33-
- Evaluating the performance impact of a synchronous-commit secondary replica
34-
35-
The dashboard provides key availability group states and performance indicators allowing you to easily make high availability operational decisions using the following types of information.
36-
37-
- Replica roll-up state
38-
39-
- Synchronization mode and state
40-
41-
- Estimate Data Loss
42-
43-
- Estimated Recovery Time (redo catch up)
44-
45-
- Database Replica details
46-
47-
- Synchronization mode and state
48-
29+
- Evaluating data-synchronization performance.
30+
- Evaluating the performance impact of a synchronous-commit secondary replica
31+
- The dashboard provides key availability group states and performance indicators allowing you to easily make high availability operational decisions using the following types of information.
32+
- Replica roll-up state
33+
- Synchronization mode and state
34+
- Estimate Data Loss
35+
- Estimated Recovery Time (redo catch up)
36+
- Database Replica details
37+
- Synchronization mode and state
4938
- Time to restore log
5039

51-
## <a name="BeforeYouBegin"></a> Before You Begin
40+
## Before You Begin
5241

53-
### <a name="Prerequisites"></a> Prerequisites
42+
### Prerequisites
5443
You must be connected to the instance of [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] (server instance) that hosts either the primary replica or a secondary replica of an availability group.
5544

56-
### <a name="Security"></a> Security
45+
### Security
5746

58-
#### <a name="Permissions"></a> Permissions
47+
#### Permissions
5948
Requires CONNECT, VIEW SERVER STATE, and VIEW ANY DEFINITION permissions.
6049

61-
## <a name="SSMSProcedure"></a> To start the Always On Dashboard
50+
## To start the Always On dashboard
6251

6352
1. In Object Explorer, connect to the instance of [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] on which you want to run the Always On Dashboard.
6453

6554
2. Expand the **Always On High Availability** node, right-click the **Availability Groups** node, and then click **Show Dashboard**.
6655

67-
### <a name="DashboardOptions"></a> To Change Always On Dashboard Options
56+
### Change Always On Dashboard Options
6857
You can use the [!INCLUDE[ssManStudioFull](../../../includes/ssmanstudiofull-md.md)]**Options** dialog box to configure the [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] Always On Dashboard behavior for automatic refreshing and enabling an auto-defined Always On policy.
6958

7059
1. From the **Tools** menu, click **Options**.
@@ -73,7 +62,7 @@ manager: craigg
7362

7463
3. To enable a user-defined policy, select **Enable user-defined Always On policy**.
7564

76-
## <a name="AvGroupsView"></a> Availability Group Summary
65+
## Availability Group Summary
7766
The availability group screen displays a summary line for each availability group for which the connected server instance hosts a replica. This pane displays the following columns.
7867

7968
**Availability Group Name**
@@ -151,7 +140,7 @@ The **Availability replica** pane displays the following columns:
151140
Lists the issue name. This value is shown by default. For a list of all the Always On policy issues, see [Always On Policies for Operational Issues with Always On Availability Groups &#40;SQL Server&#41;](../../../database-engine/availability-groups/windows/always-on-policies-for-operational-issues-always-on-availability.md).
152141

153142
**Availability Mode**
154-
Indicates the replica property that that you set separately for each availability replica. This value is hidden by default. The possible values are:
143+
Indicates the replica property that you set separately for each availability replica. This value is hidden by default. The possible values are:
155144

156145
- **Asynchronous**. The secondary replica never becomes synchronized with the primary replica.
157146

@@ -177,16 +166,11 @@ The **Availability replica** pane displays the following columns:
177166
**Operational State**
178167
Indicates the current operational state of the secondary replica. This value is hidden by default. The possible values are:
179168

180-
**0**. Pending failover
181-
182-
**1**. Pending
183-
184-
**2**. Online
185-
186-
**3**. Offline
187-
188-
**4**. Failed
189-
169+
**0**. Pending failover
170+
**1**. Pending
171+
**2**. Online
172+
**3**. Offline
173+
**4**. Failed
190174
**5**. Failed, no quorum
191175

192176
**NULL**. Replica is not local
@@ -203,17 +187,13 @@ The **Availability replica** pane displays the following columns:
203187
> [!NOTE]
204188
> For information about performance counters for availability replicas, see [SQL Server, Availability Replica](../../../relational-databases/performance-monitor/sql-server-availability-replica.md).
205189
206-
## <a name="AvDbDetails"></a> To Group Availability Group Information
190+
## Group by Availability Group information
207191
To group the information, click **Group by**, and select one of the following:
208192

209-
- **Availability replicas**
210-
211-
- **Availability databases**
212-
193+
- **Availability replicas**
194+
- **Availability databases**
213195
- **Synchronization state**
214-
215-
- **Failover readiness**
216-
196+
- **Failover readiness**
217197
- **Issues**
218198

219199
The pane that displays the grouped information displays the following columns:
@@ -227,27 +207,22 @@ The **Availability replica** pane displays the following columns:
227207
**Synchronization State**
228208
Indicates whether the availability database is currently synchronized with primary replica. This value is shown by default. The possible synchronization states are:
229209

230-
- **Not synchronizing**.
231-
232-
- For the primary role, indicates that the database is not ready to synchronize its transaction log with the corresponding secondary databases.
233-
210+
- **Not synchronizing**:
211+
-
212+
- For the primary role, indicates that the database is not ready to synchronize its transaction log with the corresponding secondary databases.
234213
- For a secondary database, indicates that the database has not started log synchronization because of a connection issue, is being suspended, or is going through transition states during startup or a role switch.
235214

236-
- **Synchronizing**.
237-
238-
On a primary replica:
239-
240-
- For a primary database, indicates that this database is ready to accept a scan request from a secondary database.
241-
242-
- On a secondary replica, indicates that there is active data movement going on for that secondary database.
215+
- **Synchronizing**:
216+
-
217+
On a primary replica:
218+
- On a primary database, indicates that this database is ready to accept a scan request from a secondary database.
219+
- On a secondary replica, indicates that there is active data movement going on for that secondary database.
243220

244-
On a secondary replica, indicates that there is active data movement going on for that replica.
245221

246-
- **Synchronized**.
222+
- **Synchronized**:
247223

248-
For a primary database, indicates that at least one secondary database is synchronized.
249-
250-
For a secondary database, indicates that the database is synchronized with the corresponding primary database.
224+
- For a primary database, indicates that at least one secondary database is synchronized.
225+
- For a secondary database, indicates that the database is synchronized with the corresponding primary database.
251226

252227
- **Reverting**.
253228

@@ -266,15 +241,13 @@ The **Availability replica** pane displays the following columns:
266241
**Failover Readiness**
267242
Indicates which availability replica can be failed over with or without potential data loss. This column is shown by default. The possible values are:
268243

269-
- **Data Loss**
270-
244+
- **Data Loss**
271245
- **No Data Loss**
272246

273247
**Issues**
274248
Lists the issue name. This column is shown by default. The possible values are:
275249

276-
- **Warnings**. Click to display the thresholds and warnings issues.
277-
250+
- **Warnings**. Click to display the thresholds and warnings issues.
278251
- **Critical**. Click to display the critical issues.
279252

280253
For a list of all the Always On policy issues, see [Always On Policies for Operational Issues with Always On Availability Groups &#40;SQL Server&#41;](../../../database-engine/availability-groups/windows/always-on-policies-for-operational-issues-always-on-availability.md).
@@ -295,13 +268,13 @@ The **Availability replica** pane displays the following columns:
295268
Indicates the time in seconds it takes to synchronize between the primary and secondary replicas. This value is hidden by default.
296269

297270
**Log Send Queue Size (KB)**
298-
Indicates the amount of log records in the log files of the primary database that have not been sent to the secondary replica. This value is hidden by default.
271+
Indicates the number of log records in the log files of the primary database that have not been sent to the secondary replica. This value is hidden by default.
299272

300273
**Log Send Rate (KB/sec)**
301-
Indicates the rate in KB per second at which log records are being sent to the secondary replica This value is hidden by default.
274+
Indicates the rate in KB per second at which log records are being sent to the secondary replica. This value is hidden by default.
302275

303276
**Redo Queue Size (KB)**
304-
Indicates the amount of log records in the log files of the secondary replica that have not yet been redone. This value is hidden by default.
277+
Indicates the number of log records in the log files of the secondary replica that have not yet been redone. This value is hidden by default.
305278

306279
**Redo Rate (KB/sec)**
307280
Indicates the rate in KB per second at which the log records are being redone. This value is hidden by default.
@@ -347,8 +320,16 @@ The **Availability replica** pane displays the following columns:
347320

348321
**Last Redone Time**
349322
Indicates the time when the last log record was redone on the secondary database. This value is hidden by default.
350-
351-
## <a name="RelatedTasks"></a> Related Tasks
323+
324+
325+
## Always On Availability Group latency reports
326+
The availability group latency report is a reporting tool built into the availability group dashboard and available in the [SQL Server Management Studio 17.4](../../../ssms/download-sql-server-management-studio-ssms.md) release. This feature provides an easy-to-understand report detailing time spent during various phases of the log transport process. This provides a way to narrow down the potential cause of latency during the synchronization process.
327+
328+
SQL Agent runs the data collection and must be enabled on both the primary replica, and at least one of the secondary replicas. View the report by right-clicking the availability group > Reports > Standard Reports in **Object Explorer** of SQL Server Management Studio.
329+
330+
For more information, please see [Always On Availability Group latency reports](https://blogs.msdn.microsoft.com/sql_server_team/new-in-ssms-always-on-availability-group-latency-reports/).
331+
332+
## Related Tasks
352333

353334
- [Use Always On Policies to View the Health of an Availability Group &#40;SQL Server&#41;](../../../database-engine/availability-groups/windows/use-always-on-policies-to-view-the-health-of-an-availability-group-sql-server.md)
354335

0 commit comments

Comments
 (0)