Skip to content

Commit 94e64ce

Browse files
authored
Replace Unicode chars with UTF8 (ASCII). Curly quotes are Bad.
Replacing Unicode curly apostrophes with straight apostrophes from plain ASCII. . Our article .md files are encoded as UTF8, and usually all the characters are simple ASCII <= 0x7F. But sometimes PMs or even Writers paste text in from MS Word, which can let Unicode characters sneak in. Most often these improper Unicode characters are curly apostrophes or curly quotation marks. For instance, GitHub DIff cannot handle Unicode characters, and this causes a domino-like set of problems. . Thanks. (GitHub 'MightyPen' = 'GeneMi' at Msft.) CC: @MikeRayMSFT
1 parent 9fbb92e commit 94e64ce

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

docs/includes/sql-server-ha-story.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -109,7 +109,7 @@ Another enhancement to DTC support for availability groups is that in SQL Server
109109
> DTC support can only be configured for databases in Windows Server-based SQL Server instances. If DTC is an requirement for your application, you must use Windows Server as the OS for your SQL Server deployment, and cannot use Linux.
110110
111111
#### Always on failover cluster instances
112-
Clustered installations have been a feature of SQL Server since version 6.5. FCIs are a proven method of providing availability for the entire installation of SQL Server, known as an instance. This means that everything inside the instance, including databases, SQL Server Agent jobs, linked servers, et al., will move to another server should the underlying server encounter a problem. All FCIs require some sort of shared storage, even if it is provided via networking. The FCIs resources can only be running and owned by one node at any given time. In the picture below, the first node of the cluster owns the FCI, which also means it owns the shared storage resources associated with it denoted by the solid line to the storage.
112+
Clustered installations have been a feature of SQL Server since version 6.5. FCIs are a proven method of providing availability for the entire installation of SQL Server, known as an instance. This means that everything inside the instance, including databases, SQL Server Agent jobs, linked servers, et al., will move to another server should the underlying server encounter a problem. All FCIs require some sort of shared storage, even if it is provided via networking. The FCI's resources can only be running and owned by one node at any given time. In the picture below, the first node of the cluster owns the FCI, which also means it owns the shared storage resources associated with it denoted by the solid line to the storage.
113113

114114
![Failover Cluster Instance][BasicFCI]
115115

@@ -128,7 +128,7 @@ The list below highlights some differences with FCIs on Windows Server versus Li
128128
* The common name used by FCIs in Linux is defined in DNS, and should be the same as the resource created for the FCI.
129129

130130
#### Log shipping
131-
If recovery point and recovery time objectives are more flexible, or databases are not considered to be highly mission critical, log shipping is another proven availability feature in SQL Server. Based on SQL Servers native backups, the process for log shipping automatically generates transaction log backups, copies them to one or more instances known as a warm standby, and automatically applies the transaction log backups to that standby. Log shipping uses SQL Server Agent jobs to automate the process of backing up, copying, and applying the transaction log backups.
131+
If recovery point and recovery time objectives are more flexible, or databases are not considered to be highly mission critical, log shipping is another proven availability feature in SQL Server. Based on SQL Server's native backups, the process for log shipping automatically generates transaction log backups, copies them to one or more instances known as a warm standby, and automatically applies the transaction log backups to that standby. Log shipping uses SQL Server Agent jobs to automate the process of backing up, copying, and applying the transaction log backups.
132132
> [!IMPORTANT]
133133
> On Linux, SQL Server Agent jobs is not included as part of the installation of SQL Server itself. It is available in the package mssql-server-Agent jobs which must also be installed to use log shipping.
134134

0 commit comments

Comments
 (0)