Lokasi ngalangkungan proxy:   [ UP ]  
[Ngawartoskeun bug]   [Panyetelan cookie]                
Skip to content

Commit db2c339

Browse files
v-aljev-alje
committed
Bringing even with master.
2 parents 6d8a720 + 0a278e8 commit db2c339

9 files changed

Lines changed: 171 additions & 48 deletions

File tree

‎docs/database-engine/availability-groups/windows/availability-group-system-object-reference.md‎

Lines changed: 68 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,68 @@
1+
---
2+
title: "Always On availability group system object reference | Microsoft Docs"
3+
ms.custom: ""
4+
ms.date: "04/03/2010"
5+
ms.prod: sql
6+
ms.reviewer: ""
7+
ms.technology: high-availability
8+
ms.topic: conceptual
9+
author: MashaMSFT
10+
ms.author: mathoma
11+
manager: craigg
12+
monikerRange: ">=sql-server-2014||=sqlallproducts-allversions"
13+
---
14+
# Always On availability group system object reference
15+
16+
[!INCLUDE[appliesto-ss-xxxx-xxxx-xxx-md-winonly](../../../includes/appliesto-ss-xxxx-xxxx-xxx-md-winonly.md)]
17+
18+
This topic serves as a reference page to all the various system objects that can be used when working with Always On availability groups.
19+
20+
## System catalog views
21+
22+
| System catalog view | Description|
23+
| :------ | :----------------------------- |
24+
| [sys.availability_databases_cluster](../../../relational-databases/system-catalog-views/sys-availability-databases-cluster-transact-sql.md) | Contains one row for each availability database on the instance of SQL Server that is hosting an availability replica for any Always On availability group in the Windows Server Failover Clustering (WSFC) cluster, regardless of whether the local copy database has been joined to the availability group yet. |
25+
| [sys.availability_group_listener_ip_addresses](../../../relational-databases/system-catalog-views/sys-availability-group-listener-ip-addresses-transact-sql.md) | Returns a row for every IP address that is associated with any Always On availability group listener in the Windows Server Failover Clustering (WSFC) cluster. |
26+
| [sys.availability_group_listeners](../../../relational-databases/system-catalog-views/sys-availability-group-listeners-transact-sql.md) | For each Always On availability group, returns either zero rows indicating that no network name is associated with the availability group, or returns a row for each availability-group listener configuration in the Windows Server Failover Clustering (WSFC) cluster. |
27+
| [sys.availability_groups](../../../relational-databases/system-catalog-views/sys-availability-groups-transact-sql.md) | Returns a row for each availability group for which the local instance of SQL Server hosts an availability replica. Each row contains a cached copy of the availability group metadata. |
28+
| [sys.availability_groups_cluster](../../../relational-databases/system-catalog-views/sys-availability-groups-cluster-transact-sql.md) | Returns a row for each Always On availability group in the Windows Server Failover Clustering (WSFC) . Each row contains the availability group metadata from the WSFC cluster. |
29+
| [sys.availability_read_only_routing_lists](../../../relational-databases/system-catalog-views/sys-availability-read-only-routing-lists-transact-sql.md) | Returns a row for the read only routing list of each availability replica in an Always On availability group in the WSFC failover cluster. |
30+
| [sys.availability_replicas](../../../relational-databases/system-catalog-views/sys-availability-replicas-transact-sql.md) | Returns a row for each of the availability replicas that belong to any Always On availability group in the WSFC failover cluster. |
31+
|   |   |
32+
33+
## System dynamic management views
34+
35+
36+
| System dynamic management view | Description|
37+
| :------ | :----------------------------- |
38+
| [sys.dm_hadr_auto_page_repair](../../../relational-databases/system-dynamic-management-views/sys-dm-hadr-auto-page-repair-transact-sql.md) | Returns a row for every automatic page-repair attempt on any availability database on an availability replica that is hosted for any availability group by the server instance. |
39+
| [sys.dm_hadr_availability_group_states](../../../relational-databases/system-dynamic-management-views/sys-dm-hadr-availability-group-states-transact-sql.md) | Returns a row for each Always On availability group that possesses an availability replica on the local instance of SQL Server. Each row displays the states that define the health of a given availability group. |
40+
| [sys.dm_hadr_availability_replica_cluster_nodes](../../../relational-databases/system-dynamic-management-views/sys-dm-hadr-availability-replica-cluster-nodes-transact-sql.md) | Returns a row for every availability replica (regardless of join state) of the Always On availability groups in the Windows Server Failover Clustering (WSFC) cluster |
41+
| [sys.dm_hadr_availability_replica_cluster_states](../../../relational-databases/system-dynamic-management-views/sys-dm-hadr-availability-replica-cluster-states-transact-sql.md) | Returns a row for each Always On availability replica (regardless of its join state) of all Always On availability groups (regardless of replica location) in the Windows Server Failover Clustering (WSFC) cluster. |
42+
| [sys.dm_hadr_availability_replica_states](../../../relational-databases/system-dynamic-management-views/sys-dm-hadr-availability-replica-states-transact-sql.md) | Returns a row for each local replica and a row for each remote replica in the same Always On availability group as a local replica. Each row contains information about the state of a given replica. |
43+
| [sys.dm_hadr_cluster](../../../relational-databases/system-dynamic-management-views/sys-dm-hadr-cluster-transact-sql.md) | Returns a row that exposes the cluster name and information about the quorum |
44+
| [sys.dm_hadr_cluster_members](../../../relational-databases/system-dynamic-management-views/sys-dm-hadr-cluster-members-transact-sql.md) | Returns a row for each of the members that constitute the quorum and the state of each of them |
45+
| [sys.dm_hadr_cluster_networks](../../../relational-databases/system-dynamic-management-views/sys-dm-hadr-cluster-networks-transact-sql.md) | Returns a row for every WSFC cluster member that is participating in an availability group's subnet configuration. |
46+
| [sys.dm_hadr_database_replica_cluster_states](../../../relational-databases/system-dynamic-management-views/sys-dm-hadr-database-replica-cluster-states-transact-sql.md) | Returns a row containing information intended to provide you with insight into the health of the availability databases in the Always On availability groups in each Always On availability group on the Windows Server Failover Clustering (WSFC) cluster. |
47+
| [sys.dm_hadr_database_replica_states](../../../relational-databases/system-dynamic-management-views/sys-dm-hadr-database-replica-states-transact-sql.md) | Returns a row for each database that is participating in an Always On availability group for which the local instance of SQL Server is hosting an availability replica. |
48+
| [sys.dm_hadr_instance_node_map](../../../relational-databases/system-dynamic-management-views/sys-dm-hadr-instance-node-map-transact-sql.md) | For every instance of SQL Server that hosts an availability replica that is joined to its Always On availability group, returns the name of the Windows Server Failover Cluster (WSFC) node that hosts the server instance. |
49+
| [sys.dm_hadr_name_id_map](../../../relational-databases/system-dynamic-management-views/sys-dm-hadr-name-id-map-transact-sql.md) | Shows the mapping of Always On availability groups that the current instance of SQL Server has joined to three unique IDs: an availability group ID, a WSFC resource ID, and a WSFC Group ID. |
50+
| [sys.dm_tcp_listener_states](../../../relational-databases/system-dynamic-management-views/sys-dm-tcp-listener-states-transact-sql.md) | Returns a row containing dynamic-state information for each TCP listener. |
51+
|   |   |
52+
53+
## System functions
54+
55+
56+
| System function | Description|
57+
| :------ | :----------------------------- |
58+
| [sys.fn_hadr_is_primary_replica](../../../relational-databases/system-functions/sys-fn-hadr-is-primary-replica-transact-sql.md) | Used to determine if the current replica is the primary replica. |
59+
| [sys.fn_hadr_backup_is_preferred_replica](../../../relational-databases/system-functions/sys-fn-hadr-backup-is-preferred-replica-transact-sql.md) | Used to determine if the current replica is the preferred backup replica. |
60+
| [sys.fn_hadr_distributed_ag_replica](../../../relational-databases/system-functions/sys-fn-hadr-distributed-ag-replica-transact-sql.md) | Used to map a replica in a distributed availability group to the local availability group. |
61+
|   |   |
62+
63+
64+
65+
## See Also
66+
[Overview of Always On Availability Groups (SQL Server)](../../../database-engine/availability-groups/windows/overview-of-always-on-availability-groups-sql-server.md)
67+
68+

‎docs/database-engine/database-mirroring/database-mirroring-system-object-reference.md‎

Lines changed: 47 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,47 @@
1+
---
2+
title: "Database mirroring system object reference | Microsoft Docs"
3+
ms.custom: ""
4+
ms.date: "03/14/2017"
5+
ms.prod: sql
6+
ms.prod_service: high-availability
7+
ms.reviewer: ""
8+
ms.technology: high-availability
9+
ms.topic: conceptual
10+
author: MashaMSFT
11+
ms.author: mathoma
12+
manager: craigg
13+
---
14+
# Database mirroring system object reference
15+
[!INCLUDE[appliesto-ss-xxxx-xxxx-xxx-md](../../includes/appliesto-ss-xxxx-xxxx-xxx-md.md)]
16+
17+
## System catalog views
18+
19+
| System catalog view | Description|
20+
| :------ | :----------------------------- |
21+
| [sys.database_mirroring_witnesses](../../relational-databases/system-catalog-views/database-mirroring-witness-catalog-views-sys-database-mirroring-witnesses.md) | Contains a row for every witness role that a server plays in a database mirroring partnership. |
22+
|   |   |
23+
24+
## System dynamic management views
25+
26+
| System dynamic management view | Description|
27+
| :------ | :----------------------------- |
28+
| [sys.dm_db_mirroring_auto_page_repair](../../relational-databases/system-dynamic-management-views/database-mirroring-sys-dm-db-mirroring-auto-page-repair.md) | Returns a row for every automatic page-repair attempt on any mirrored database on the server instance. |
29+
| [sys.dm_db_mirroring_connections](../../relational-databases/system-dynamic-management-views/database-mirroring-sys-dm-db-mirroring-connections.md) | Returns a row for each connection established for database mirroring. |
30+
|   |   |
31+
32+
## System tables
33+
34+
| System table | Description|
35+
| :------ | :----------------------------- |
36+
| [sysdbmaintplan_databases](../../relational-databases/system-tables/sysdbmaintplan-databases-transact-sql.md) | Returns information about database mirroring maintenance plans. |
37+
| [sysdbmaintplan_history](../../relational-databases/system-tables/sysdbmaintplan-history-transact-sql.md) | Returns information about the history of database mirroring maintenance plans. |
38+
| [sysdbmaintplan_jobs](../../relational-databases/system-tables/sysdbmaintplan-jobs-transact-sql.md) |Returns information about database mirroring maintenance plans jobs. |
39+
| [sysdbmaintplans](../../relational-databases/system-tables/sysdbmaintplans-transact-sql.md) | Returns information about database mirroring plans. |
40+
|   |   |
41+
42+
43+
## See Also
44+
[Database Mirroring (SQL Server)](../../database-engine/database-mirroring/database-mirroring-sql-server.md)
45+
46+
47+

‎docs/linux/sql-server-linux-create-availability-group.md‎

Lines changed: 10 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -66,7 +66,7 @@ sudo systemctl restart mssql-server
6666

6767
An availability group uses TCP endpoints for communication. Under Linux, endpoints for an AG are only supported if certificates are used for authentication. This means that the certificate from one instance must be restored on all other instances that will be replicas participating in the same AG. The certificate process is required even for a configuration-only replica.
6868

69-
Creating endpoints and restoring certificates can only be done via Transact-SQL. You can use non- [!INCLUDE[ssnoversion-md](../includes/ssnoversion-md.md)]-generated certificates as well. You will also need a process to manage and replace any certificates that expire.
69+
Creating endpoints and restoring certificates can only be done via Transact-SQL. You can use non- [!INCLUDE[ssnoversion-md](../includes/ssnoversion-md.md)]-generated certificates as well. You will also need a process to manage and replace any certificates that expire.
7070

7171
> [!IMPORTANT]
7272
> If you plan to use the [!INCLUDE[ssmanstudiofull-md](../includes/ssmanstudiofull-md.md)] wizard to create the AG, you still need to create and restore the certificates by using Transact-SQL on Linux.
@@ -238,7 +238,7 @@ This example will create certificates for a three-node configuration. The instan
238238
GO
239239
```
240240
241-
10. Restore LinAGN1_Cert and LinAGN3_Cert on LinAGN2.
241+
10. Restore LinAGN1_Cert and LinAGN3_Cert on LinAGN2.
242242
243243
```SQL
244244
CREATE CERTIFICATE LinAGN1_Cert
@@ -252,8 +252,9 @@ This example will create certificates for a three-node configuration. The instan
252252
FROM FILE = '/var/opt/mssql/data/LinAGN3_Cert.cer';
253253
254254
GO
255+
```
255256
256-
11. Grant the logins associated with LinAG1 and LinAGN3 permission to connect to the endpoint on LinAGN2.
257+
11. Grant the logins associated with LinAG1 and LinAGN3 permission to connect to the endpoint on LinAGN2.
257258
258259
```SQL
259260
GRANT CONNECT ON ENDPOINT::AGEP TO LinAGN1_Login;
@@ -265,7 +266,7 @@ This example will create certificates for a three-node configuration. The instan
265266
GO
266267
```
267268
268-
12. Create the instance-level logins and users associated with LinAGN1 and LinAGN2 on LinAGN3.
269+
12. Create the instance-level logins and users associated with LinAGN1 and LinAGN2 on LinAGN3.
269270
270271
```SQL
271272
CREATE LOGIN LinAGN1_Login WITH PASSWORD = '<StrongPassword>';
@@ -279,7 +280,7 @@ This example will create certificates for a three-node configuration. The instan
279280
GO
280281
```
281282
282-
13. Restore LinAGN1_Cert and LinAGN2_Cert on LinAGN3.
283+
13. Restore LinAGN1_Cert and LinAGN2_Cert on LinAGN3.
283284
284285
```SQL
285286
CREATE CERTIFICATE LinAGN1_Cert
@@ -293,8 +294,9 @@ This example will create certificates for a three-node configuration. The instan
293294
FROM FILE = '/var/opt/mssql/data/LinAGN2_Cert.cer';
294295
295296
GO
297+
```
296298
297-
14. Grant the logins associated with LinAG1 and LinAGN2 permission to connect to the endpoint on LinAGN3.
299+
14. Grant the logins associated with LinAG1 and LinAGN2 permission to connect to the endpoint on LinAGN3.
298300
299301
```SQL
300302
GRANT CONNECT ON ENDPOINT::AGEP TO LinAGN1_Login;
@@ -411,7 +413,7 @@ This example shows how to create a two-replica AG that uses a configuration-only
411413
GO
412414
```
413415

414-
3. In a query window connected to the configuration only replica, join it to the AG.
416+
3. In a query window connected to the configuration only replica, join it to the AG.
415417

416418
```SQL
417419
ALTER AVAILABILITY GROUP [<AGName>] JOIN WITH (CLUSTER_TYPE = EXTERNAL);
@@ -534,7 +536,7 @@ A Pacemaker high availability cluster underlying [!INCLUDE[ssnoversion-md](../in
534536
1. In a query window connected to the first replica, execute the following:
535537

536538
```SQL
537-
CREATE LOGIN PMLogin WITH PASSWORD '<StrongPassword>';
539+
CREATE LOGIN PMLogin WITH PASSWORD ='<StrongPassword>';
538540
539541
GO
540542

‎docs/relational-databases/backup-restore/create-a-full-database-backup-sql-server.md‎

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -205,19 +205,19 @@ A stored access policy has been created with read, write, and list rights. The
205205
*
206206
5. Select `https://mystorageaccount.blob.core.windows.net/myfirstcontainer` from the **Azure storage container:** text box
207207

208-
6. In the **Backup File:** text box enter `Sales_stripe1of2_20160601.bak`.
208+
6. In the **Backup File:** text box enter `Sales_stripe1of2_20160601.bak`.
209209

210-
7. Click **OK**.
210+
7. Click **OK**.
211211

212-
8. Repeat Steps **4** and **5**.
212+
8. Repeat Steps **4** and **5**.
213213

214-
9. In the **Backup File:** text box enter `Sales_stripe2of2_20160601.bak`.
214+
9. In the **Backup File:** text box enter `Sales_stripe2of2_20160601.bak`.
215215

216-
10. Click **OK**.
216+
10. Click **OK**.
217217

218-
11. Click **OK**.
218+
11. Click **OK**.
219219

220-
**D2. A shared access signature exists and a SQL Server Credential does not exist**
220+
**D2. A shared access signature exists and a SQL Server Credential does not exist**
221221
5. Enter `https://mystorageaccount.blob.core.windows.net/myfirstcontainer` in the **Azure storage container:** text box
222222

223223
6. Enter the shared access signature in the **Shared Access Policy:** text box.

0 commit comments

Comments
 (0)