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

Commit 2963453

Browse files
MashaMSFTMashaMSFT
committed
Git Issue fixes
1 parent 0ee46d5 commit 2963453

2 files changed

Lines changed: 58 additions & 22 deletions

File tree

‎docs/database-engine/availability-groups/windows/listeners-client-connectivity-application-failover.md‎

Lines changed: 44 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -127,16 +127,52 @@ Server=tcp:AGListener,1433;Database=AdventureWorks;Integrated Security=SSPI; Mul
127127

128128
## <a name="SSLcertificates"></a> Listeners & SSL certificates
129129

130-
When connecting to an availability group listener, if the participating instances of SQL Server use SSL certificates in conjunction with session encryption, the connecting client driver will need to support the Subject Alternate Name in the SSL certificate in order to force encryption. SQL Server driver support for certificate Subject Alternative Name is planned for ADO.NET (SqlClient), Microsoft JDBC, and SQL Native Client (SNAC).
130+
When connecting to an availability group listener, if the participating instances of SQL Server use SSL certificates in conjunction with session encryption, the connecting client driver will need to support the Subject Alternate Name in the SSL certificate in order to force encryption. SQL Server driver support for certificate Subject Alternative Name is planned for ADO.NET (SqlClient), Microsoft JDBC, and SQL Native Client (SNAC).
131131

132-
An X.509 certificate must be configured for each participating server node in the failover cluster with a list of all availability group listeners set in the Subject Alternate Name of the certificate.
133-
134-
For example, if the WSFC has three availability group listeners with the names `AG1_listener.Adventure-Works.com`, `AG2_listener.Adventure-Works.com`, and `AG3_listener.Adventure-Works.com`, the Subject Alternative Name for the certificate should be set as follows:
135-
136-
```
137-
CN = ServerFQDN
138-
SAN = ServerFQDN,AG1_listener.Adventure-Works.com, AG2_listener.Adventure-Works.com, AG3_listener.Adventure-Works.com
132+
An X.509 certificate must be configured for each participating server node in the failover cluster with a list of all availability group listeners set in the Subject Alternate Name of the certificate.
133+
134+
The format for the certificate values is:
135+
139136
```
137+
CN = Server.FQDN
138+
SAN = Server.FQDN,Listener1.FQDN,Listener2.FQDN
139+
```
140+
141+
For example, you have the following values:
142+
143+
```
144+
Servername: Win2019
145+
Instance: SQL2019
146+
AG: AG2019
147+
Listener: Listener2019
148+
Domain: contoso.com (which is also the FQDN)
149+
```
150+
151+
For a WSFC that has a single availability group, the certificate should have the fully qualified domain name (FQDN) of the server, and the FQDN of the listener:
152+
153+
```
154+
CN: Win2019.contoso.com
155+
SAN: Win2019.contoso.com, Listener2019.contoso.com
156+
```
157+
158+
With this configuration, your connections will be encrypted when connecting to the instance (`WIN2019\SQL2019`), or the the listener (`Listener2019`).
159+
160+
Depending on how networking is configured, there is a small subset of customers that may need to add the NetBIOS to the SAN as well. In which case, the certificate values should be:
161+
162+
```
163+
CN: Win2019.contoso.com
164+
SAN: Win2019,Win2019.contoso.com,Listener2019,Listener2019.contoso.com
165+
```
166+
167+
If the WSFC has three availability group listeners, such as: Listener1, Listener2, Listener3
168+
169+
Then the certificate values should be:
170+
171+
```
172+
CN: Win2019.contoso.com
173+
SAN: Win2019.contoso.com,Listener1.contoso.com,Listener2.contoso.com,Listener3.contoso.com
174+
```
175+
140176

141177
## <a name="SPNs"></a> Listeners and Kerberos (SPNs)
142178

‎docs/sql-server/install/work-with-multiple-versions-and-instances-of-sql-server.md‎

Lines changed: 14 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -32,9 +32,8 @@ The following SQL Server-related items are compatible with the installation of m
3232

3333
- Analysis Services
3434

35-
::: moniker range="=sql-server-2016||=sqlallproducts-allversions"
36-
- Reporting Services
37-
::: moniker-end
35+
- Reporting Services (in SQL Server 2016, and previous). Starting with SQL Server 2016. SQL Server Reporting Services (SSRS) has a separate installation.
36+
3837

3938
You can upgrade earlier versions of SQL Server on a computer where other SQL Server versions are already installed. For supported upgrade scenarios, see [Supported Version and Edition Upgrades](../../database-engine/install-windows/supported-version-and-edition-upgrades.md).
4039

@@ -89,23 +88,24 @@ For more information about [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.
8988
## Using [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] Side-By-Side with Previous Versions of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)]
9089

9190
You can install [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] on a computer that is already running instances of an earlier [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] version. If a default instance already exists on the computer, [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] must be installed as a named instance.
91+
92+
The following table shows side-by-side support for each version of SQL Server on commonly supported versions of Windows:
93+
94+
| Existing instance | Side by side support|
95+
|-------------------|----------------------------|
96+
| SQL Server 2019 | SQL Server 2008 through SQL Server 2017|
97+
| SQL Server 2017 | SQL Server 2008 through SQL Server 2016|
98+
| SQL Server 2016 | SQL Server 2008 through SQL Server 2014|
99+
100+
101+
92102

93103
> [!CAUTION]
94104
> [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] SysPrep does not support side by side installation of prepared instances of [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)] with earlier versions of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] on the same computer. For example, you cannot prepare a [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)] instance side by side with a prepared instance of [!INCLUDE[ssSQL11](../../includes/sssql11-md.md)]. However, you can install multiple prepared instances of the same major version of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] side by side on the same computer. For more information, see [Considerations for Installing SQL Server Using SysPrep](../../database-engine/install-windows/considerations-for-installing-sql-server-using-sysprep.md).
95105
>
96-
> [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)] cannot be installed side-by-side with earlier versions of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] on a computer that is running Windows Server 2008 R2 Server Core SP1. For more information on Server Core installations, see [Install SQL Server 2016 on Server Core](../../database-engine/install-windows/install-sql-server-on-server-core.md).
106+
> SQL Server 2016 and greater cannot be installed side-by-side with earlier versions of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] on a computer that is running Windows Server 2008 R2 Server Core SP1. For more information on Server Core installations, see [Install SQL Server 2016 on Server Core](../../database-engine/install-windows/install-sql-server-on-server-core.md).
97107
98-
The following table shows side-by-side support for [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]:
99-
100-
|Existing instance of [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]|side by side support|
101-
|--------------------------------------------------|----------------------------|
102-
|[!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)] (64-bit) [!INCLUDE[vcprx64](../../includes/vcprx64-md.md)]|[!INCLUDE[ssVersion2005](../../includes/ssversion2005-md.md)] (32-bit)<br /><br /> [!INCLUDE[ssVersion2005](../../includes/ssversion2005-md.md)] (64-bit) [!INCLUDE[vcprx64](../../includes/vcprx64-md.md)]<br /><br /> [!INCLUDE[ssKatmai](../../includes/sskatmai-md.md)] (32-bit)<br /><br /> [!INCLUDE[ssKatmai](../../includes/sskatmai-md.md)] (64-bit) [!INCLUDE[vcprx64](../../includes/vcprx64-md.md)]<br /><br /> [!INCLUDE[ssKilimanjaro](../../includes/sskilimanjaro-md.md)] (32-bit)<br /><br /> [!INCLUDE[ssKilimanjaro](../../includes/sskilimanjaro-md.md)] (64-bit) [!INCLUDE[vcprx64](../../includes/vcprx64-md.md)]<br /><br /> [!INCLUDE[ssSQL11](../../includes/sssql11-md.md)] (32-bit)<br /><br /> [!INCLUDE[ssSQL11](../../includes/sssql11-md.md)] (64-bit) [!INCLUDE[vcprx64](../../includes/vcprx64-md.md)]<br /><br /> [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] (32-bit)<br /><br /> [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] (64-bit) [!INCLUDE[vcprx64](../../includes/vcprx64-md.md)] <br /><br /> [!INCLUDE[ssSQL15](../../includes/sssql15-md.md)]|
103-
104-
The following table shows side-by-side support for [!INCLUDE[ssSQL15](../../includes/sssql15-md.md)] with previous versions:
105108

106-
|Existing instance of [!INCLUDE[ssSQL15](../../includes/sssql15-md.md)]|Side-by-side support for previous versions|
107-
|--------------------------------------------------|----------------------------|
108-
|[!INCLUDE[ssSQL15](../../includes/sssql15-md.md)] [!INCLUDE[vcprx64](../../includes/vcprx64-md.md)]|[!INCLUDE[ssVersion2005](../../includes/ssversion2005-md.md)] (32-bit)<br /><br /> [!INCLUDE[ssVersion2005](../../includes/ssversion2005-md.md)] (64-bit) [!INCLUDE[vcprx64](../../includes/vcprx64-md.md)]<br /><br /> [!INCLUDE[ssKatmai](../../includes/sskatmai-md.md)] (32-bit)<br /><br /> [!INCLUDE[ssKatmai](../../includes/sskatmai-md.md)] (64-bit) [!INCLUDE[vcprx64](../../includes/vcprx64-md.md)]<br /><br /> [!INCLUDE[ssKilimanjaro](../../includes/sskilimanjaro-md.md)] (32-bit)<br /><br /> [!INCLUDE[ssKilimanjaro](../../includes/sskilimanjaro-md.md)] (64-bit) [!INCLUDE[vcprx64](../../includes/vcprx64-md.md)]<br /><br /> [!INCLUDE[ssSQL11](../../includes/sssql11-md.md)] (32-bit)<br /><br /> [!INCLUDE[ssSQL11](../../includes/sssql11-md.md)] (64-bit) [!INCLUDE[vcprx64](../../includes/vcprx64-md.md)]<br /><br /> [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] (32-bit)<br /><br /> [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] (64-bit) [!INCLUDE[vcprx64](../../includes/vcprx64-md.md)]|
109109

110110
## Preventing IP Address Conflicts
111111

0 commit comments

Comments
 (0)