Skip to content

Commit 2a882da

Browse files
v-thepetv-thepet
committed
typos
1 parent 0997e0a commit 2a882da

7 files changed

Lines changed: 9 additions & 8 deletions

‎_themes.pdf‎

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
Subproject commit 6840bf50604e98969545d16a517ec9faf0040f75

‎docs/database-engine/availability-groups/windows/always-on-availability-groups-sql-server.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -33,7 +33,7 @@ ms.workload: "Active"
3333
An availability group fails over at the level of an availability replica. Failovers are not caused by database issues such as a database becoming suspect due to a loss of a data file, deletion of a database, or corruption of a transaction log.
3434

3535
>[NOTE]
36-
>Always On availability groups is the full, formal name for this availablity feature. The abbreviation is AG, not AOAG or AAG.
36+
>Always On availability groups is the full, formal name for this availability feature. The abbreviation is AG, not AOAG or AAG.
3737
3838
## <a name="Benefits"></a> Benefits
3939
[!INCLUDE[ssHADR](../../../includes/sshadr-md.md)] provides a rich set of options that improve database availability and that enable improved resource use. The key components are as follows:

‎docs/database-engine/availability-groups/windows/enhanced-database-failover.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -76,7 +76,7 @@ To disable this behavior, issue the following ALTER AVAILABILITY GROUP command:
7676
ALTER AVAILABILITY GROUP [AGNAME] SET (DB_FAILOVER = OFF)
7777
```
7878
### Dynamic management view
79-
To see whether an availability group has enhanced database failover enabled, query the dynamic management view `sys.availablity_groups`. The column `db_failover` will have a zero if disabled or 1 if enabled.
79+
To see whether an availability group has enhanced database failover enabled, query the dynamic management view `sys.availability_groups`. The column `db_failover` will have a zero if disabled or 1 if enabled.
8080

8181
## Next steps
8282

‎docs/database-engine/availability-groups/windows/overview-of-always-on-availability-groups-sql-server.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -57,7 +57,7 @@ ms.workload: "Active"
5757
5858
The following illustration shows an availability group that contains one primary replica and four secondary replicas. Up to eight secondary replicas are supported, including one primary replica and two synchronous-commit secondary replicas.
5959

60-
![Availabilty group with five replicas](../../../database-engine/availability-groups/windows/media/aoag-agintrofigure.gif "Availabilty group with five replicas")
60+
![availability group with five replicas](../../../database-engine/availability-groups/windows/media/aoag-agintrofigure.gif "availability group with five replicas")
6161

6262
## <a name="AvDbs"></a> Availability Databases
6363
To add a database to an availability group, the database must be an online, read-write database that exists on the server instance that hosts the primary replica. When you add a database, it joins the availability group as a primary database, while remaining available to clients. No corresponding secondary database exists until backups of the new primary database are restored to the server instance that hosts the secondary replica (using RESTORE WITH NORECOVERY). The new secondary database is in the RESTORING state until it is joined to the availability group. For more information, see [Start Data Movement on an Always On Secondary Database &#40;SQL Server&#41;](../../../database-engine/availability-groups/windows/start-data-movement-on-an-always-on-secondary-database-sql-server.md).

‎docs/database-engine/availability-groups/windows/upgrading-always-on-availability-group-replica-instances.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -39,7 +39,7 @@ ms.workload: "On Demand"
3939
- [Hardware and Software Requirements for Installing SQL Server 2016](../../../sql-server/install/hardware-and-software-requirements-for-installing-sql-server.md): Review the software requirements for installing [!INCLUDE[ssCurrent](../../../includes/sscurrent-md.md)]. If additional software is required, install it on each node before you begin the upgrade process to minimize any downtime.
4040

4141
> [!NOTE]
42-
> Mixing versions of SQL Server in the same AG is not supported outside of a rolling upgrade which upgrades the replicas in place. This means a higher version of SQL Server cannot be added as a new replica to an existing AG. For example, a SQL Server 2017 replica cannot be added to an existing SQL Server 2016 AG. To migrate to a new version of SQL Server using availablity groups, the only supported method is a distributed availability group which is in SQL Server 2016 Enterprise Edition or later.
42+
> Mixing versions of SQL Server in the same AG is not supported outside of a rolling upgrade which upgrades the replicas in place. This means a higher version of SQL Server cannot be added as a new replica to an existing AG. For example, a SQL Server 2017 replica cannot be added to an existing SQL Server 2016 AG. To migrate to a new version of SQL Server using availability groups, the only supported method is a distributed availability group which is in SQL Server 2016 Enterprise Edition or later.
4343
4444
## Rolling Upgrade Best Practices for Always On Availability Groups
4545
The following best practices should be observed when performing server upgrades or updates in order to minimize downtime and data loss for your availability groups:

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

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -411,7 +411,7 @@ This example shows how to create a two-replica AG that uses a configuration-only
411411
412412
GO
413413
414-
ALTER AVAILABLITY GROUP [<AGName>] GRANT CREATE ANY DATABASE;
414+
ALTER availability GROUP [<AGName>] GRANT CREATE ANY DATABASE;
415415
416416
GO
417417
```
@@ -475,7 +475,7 @@ This example shows three full replicas and how read-only routing can be configur
475475
476476
GO
477477
478-
ALTER AVAILABLITY GROUP [<AGName>] GRANT CREATE ANY DATABASE;
478+
ALTER availability GROUP [<AGName>] GRANT CREATE ANY DATABASE;
479479
480480
GO
481481
```
@@ -547,7 +547,7 @@ A Pacemaker high availability cluster underlying [!INCLUDE[ssnoversion-md](../in
547547
548548
GO
549549
550-
GRANT ALTER, CONTROL, VIEW DEFINITION ON AVAILABLITY GROUP::<AGThatWasCreated> TO PMLogin;
550+
GRANT ALTER, CONTROL, VIEW DEFINITION ON availability GROUP::<AGThatWasCreated> TO PMLogin;
551551
552552
GO
553553
```

‎docs/t-sql/language-elements/transact-sql-syntax-conventions-transact-sql.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -117,7 +117,7 @@ ms.workload: "Active"
117117
Many code examples prefix Unicode character string constants with the letter **N**. Without the **N** prefix, the string is converted to the default code page of the database. This default code page may not recognize certain characters.
118118

119119
## "Applies to" References
120-
The [!INCLUDE[tsql](../../includes/tsql-md.md)] reference includes topics related to [!INCLUDE[ssKatmai](../../includes/sskatmai-md.md)], [!INCLUDE[ssKilimanjaro](../../includes/sskilimanjaro-md.md)], [!INCLUDE[ssSQL11](../../includes/sssql11-md.md)], [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)], [!INCLUDE[ssSDSfull](../../includes/sssdsfull-md.md)], and [!INCLUDE[ssSDWfull](../../includes/sssdwfull-md.md)]. Near the top of each topic is a section indicating which products support the subject of the topic. If a product is omitted, then the feature described by the topic is not available in that product. For example, availability groups were introduced in [!INCLUDE[ssSQL11](../../includes/sssql11-md.md)]. The **CREATE AVAILABILTY GROUP** topic indicates it applies to **SQL Server (SQL Server 2012 through current version)** because it does not apply to [!INCLUDE[ssKatmai](../../includes/sskatmai-md.md)], [!INCLUDE[ssKilimanjaro](../../includes/sskilimanjaro-md.md)], or [!INCLUDE[ssSDSfull](../../includes/sssdsfull-md.md)].
120+
The [!INCLUDE[tsql](../../includes/tsql-md.md)] reference includes topics related to [!INCLUDE[ssKatmai](../../includes/sskatmai-md.md)], [!INCLUDE[ssKilimanjaro](../../includes/sskilimanjaro-md.md)], [!INCLUDE[ssSQL11](../../includes/sssql11-md.md)], [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)], [!INCLUDE[ssSDSfull](../../includes/sssdsfull-md.md)], and [!INCLUDE[ssSDWfull](../../includes/sssdwfull-md.md)]. Near the top of each topic is a section indicating which products support the subject of the topic. If a product is omitted, then the feature described by the topic is not available in that product. For example, availability groups were introduced in [!INCLUDE[ssSQL11](../../includes/sssql11-md.md)]. The **CREATE availability GROUP** topic indicates it applies to **SQL Server (SQL Server 2012 through current version)** because it does not apply to [!INCLUDE[ssKatmai](../../includes/sskatmai-md.md)], [!INCLUDE[ssKilimanjaro](../../includes/sskilimanjaro-md.md)], or [!INCLUDE[ssSDSfull](../../includes/sssdsfull-md.md)].
121121

122122
In some cases, the general subject of topic can be used in a product, but all of the arguments are not supported. For example, contained database users were introduced in [!INCLUDE[ssSQL11](../../includes/sssql11-md.md)]. The **CREATE USER** statement can be used in any [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] product, however the **WITH PASSWORD** syntax cannot be used with older versions. In this case, additional **Applies to** sections are inserted into the appropriate argument descriptions in the body of the topic.
123123

0 commit comments

Comments
 (0)