Skip to content

Commit 385a907

Browse files
huypubhuypub
authored
Merge pull request #12903 from MicrosoftDocs/master
11/13 PM Publish
2 parents d00ba0b + 084d817 commit 385a907

12 files changed

Lines changed: 91 additions & 49 deletions

‎.openpublishing.redirection.json‎

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,10 @@
11
{
22
"redirections": [
3+
{
4+
"source_path": "docs/database-engine/sql-server-database-engine-backward-compatibility.md",
5+
"redirect_url": "/sql/database-engine/discontinued-database-engine-functionality-in-sql-server",
6+
"redirect_document_id": false
7+
},
38
{
49
"source_path": "docs/database-engine/whats-new-in-sql-server-2016.md",
510
"redirect_url": "/sql/sql-server/what-s-new-in-sql-server-2016",

‎docs/advanced-analytics/install/sql-ml-component-install-without-internet-access.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: Install SQL Server machine learning R and Python on computers isola
44
ms.prod: sql
55
ms.technology: machine-learning
66

7-
ms.date: 07/30/2019
7+
ms.date: 11/04/2019
88
ms.topic: conceptual
99
author: dphansen
1010
ms.author: davidph

‎docs/big-data-cluster/concept-data-persistence.md‎

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -82,8 +82,10 @@ AKS comes with [two built-in storage classes](/azure/aks/azure-disks-dynamic-pv/
8282

8383
Kubernetes clusters deployed using `kubeadm` do not have a built-in storage class. You must create your own storage classes and persistent volumes using local storage or your preferred provisioner, such as [Rook](https://github.com/rook/rook). In that case, you would set the `className` to the storage class you configured.
8484

85-
> [!NOTE]
86-
> In the built in deployment configuration files for kubeadm (`kubeadm-dev-test` or `kubeadm-prod`) there is no storage class name specified for the data and log storage. Before deployment, you must customize the configuration file and set the value for className otherwise the pre-deployment validations will fail. Deployment also has a validation step that checks for the existence of the storage class, but not for the necessary persistent volumes. You must ensure you create enough volumes depending on the scale of your cluster. For the default minimum cluster size (default scale, no high availability) you must create at least 24 persistent volumes. [Here](https://github.com/Microsoft/sql-server-samples/tree/master/samples/features/sql-big-data-cluster/deployment/kubeadm/ubuntu) is an example on how to create persistent volumes using local provisioner.
85+
> [!IMPORTANT]
86+
> In the built in deployment configuration files for kubeadm (`kubeadm-dev-test` or `kubeadm-prod`) there is no storage class name specified for the data and log storage. Before deployment, you must customize the configuration file and set the value for `className` otherwise the pre-deployment validations will fail. Deployment also has a validation step that checks for the existence of the storage class, but not for the necessary persistent volumes. You must ensure you create enough volumes depending on the scale of your cluster. For the default minimum cluster size (default scale, no high availability) you must create at least 24 persistent volumes.
87+
>
88+
>[Create a Kubernetes cluster](https://github.com/Microsoft/sql-server-samples/tree/master/samples/features/sql-big-data-cluster/deployment/kubeadm/ubuntu) presents an example of how you can create persistent volumes using the local provisioner. This example introduces Kubernetes storage.
8789

8890

8991
## Customize storage configurations for each pool

‎docs/big-data-cluster/deployment-guidance.md‎

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -64,6 +64,11 @@ kubectl config view
6464
6565
After you have configured your Kubernetes cluster, you can proceed with the deployment of a new SQL Server big data cluster. If you are upgrading from a previous release, please see [How to upgrade [!INCLUDE[big-data-clusters-2019](../includes/ssbigdataclusters-ss-nover.md)]](deployment-upgrade.md).
6666

67+
## Ensure you have storage configured
68+
It's important for most big data cluster deployments to have persistent storage. At this time, you need to make sure you have a plan for how you're going to provide persistent storage on the Kubernetes cluster *before* you deploy the BDC tools.
69+
70+
If you're using AKS and you plan to use dynamically provisioned storage, you should set up a persistent volume claim on your preferred storage class now. If you aren't planning to use AKS's dynamically provisioned storage (e.g. because you're deploying on your own kubeadm cluster), you'll need to ensure you have sufficient storage for a cluster of your desired scale available and configured for use. If you wish to customize how your storage is used, you should do this before proceeding. See [Data persistence with SQL Server big data cluster on Kubernetes](concept-data-persistence.md).
71+
6772
## <a id="deploy"></a> Deployment overview
6873

6974
Most big data cluster settings are defined in a JSON deployment configuration file. You can use a default deployment profile for AKS and Kubernetes clusters created with `kubeadm` or you can customize your own deployment configuration file to use during setup. For security reasons, authentication settings are passed via environment variables.

‎docs/database-engine/breaking-changes-to-database-engine-features-in-sql-server-version-15.md‎

Lines changed: 27 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,27 @@
1+
---
2+
title: "Breaking changes to database engine | Microsoft Docs"
3+
description: "Breaking changes to database engine features in SQL Server 2019"
4+
ms.date: "11/27/2018"
5+
ms.prod: sql
6+
ms.prod_service: high-availability
7+
ms.reviewer: ""
8+
ms.custom: ""
9+
ms.technology: release-landing
10+
ms.topic: conceptual
11+
helpviewer_keywords:
12+
- "breaking changes 2017 [SQL Server]"
13+
ms.assetid:
14+
author: MikeRayMSFT
15+
ms.author: mikeray
16+
monikerRange: ">=sql-server-2017||=sqlallproducts-allversions||>=sql-server-linux-2017"
17+
---
18+
# Breaking changes to database engine in [!INCLUDE[sssqlv15-md](../includes/sssqlv15-md.md)]
19+
[!INCLUDE[tsql-appliesto-sssver15-xxxx-xxxx-xxx-md](../includes/tsql-appliesto-ssver15-xxxx-xxxx-xxx.md)]
20+
21+
SQL Server 2019 does not introduce breaking changes.
22+
23+
### See also
24+
25+
- [Deprecated database engine features in SQL Server 2019](../database-engine/deprecated-database-engine-features-in-sql-server-version-15.md)
26+
- [Discontinued database engine functionality in SQL Server](../database-engine/discontinued-database-engine-functionality-in-sql-server.md)
27+
- [SQL Server database engine backward compatibility](../database-engine/sql-server-database-engine-backward-compatibility.md)

‎docs/database-engine/deprecated-database-engine-features-in-sql-server-version-15.md‎

Lines changed: 27 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,27 @@
1+
---
2+
title: "Deprecated database engine features | Microsoft Docs"
3+
description: "Deprecated Database Engine features in SQL Server 2019"
4+
ms.date: "11/27/2018"
5+
ms.prod: sql
6+
ms.prod_service: high-availability
7+
ms.reviewer: ""
8+
ms.custom: ""
9+
ms.technology: release-landing
10+
ms.topic: conceptual
11+
helpviewer_keywords:
12+
- "deprecated changes 2019 [SQL Server]"
13+
ms.assetid:
14+
author: MikeRayMSFT
15+
ms.author: mikeray
16+
monikerRange: ">=sql-server-ver15||=sqlallproducts-allversions||>=sql-server-linux-ver15"
17+
---
18+
# Deprecated database engine features in [!INCLUDE[sssqlv15-md](../includes/sssqlv15-md.md)]
19+
[!INCLUDE[tsql-appliesto-sssver15-xxxx-xxxx-xxx-md](../includes/tsql-appliesto-ssver15-xxxx-xxxx-xxx.md)]
20+
21+
SQL Server 2019 does not deprecate any features.
22+
23+
### See Also
24+
25+
- [Breaking changes to database engine features in SQL Server 2019](../database-engine/breaking-changes-to-database-engine-features-in-sql-server-version-15.md)
26+
- [Discontinued database engine functionality in SQL Server](../database-engine/discontinued-database-engine-functionality-in-sql-server.md)
27+
- [SQL Server database engine backward compatibility](../database-engine/sql-server-database-engine-backward-compatibility.md)

‎docs/database-engine/discontinued-database-engine-functionality-in-sql-server.md‎

Lines changed: 9 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: "Discontinued Database Engine Functionality in SQL Server | Microsoft Docs"
2+
title: "Discontinued database engine functionality in SQL Server | Microsoft Docs"
33
ms.custom: ""
44
ms.date: "02/02/2017"
55
ms.prod: sql
@@ -70,7 +70,12 @@ For current configuration options, see [ALTER DATABASE SCOPED CONFIGURATION (Tra
7070

7171
- [Discontinued Database Engine Functionality in SQL Server 2014](https://docs.microsoft.com/sql/database-engine/discontinued-database-engine-functionality-in-sql-server-2016?view=sql-server-2014)
7272

73-
## See Also
73+
### See also
7474

75-
- [Deprecated Database Engine Features in SQL Server 2016](../database-engine/deprecated-database-engine-features-in-sql-server-2016.md)
76-
- [Deprecated Features in SQL Server Replication](../relational-databases/replication/deprecated-features-in-sql-server-replication.md)
75+
- [Deprecated database engine features in SQL Server 2019](deprecated-database-engine-features-in-sql-server-version-15.md)
76+
- [Deprecated database engine features in SQL Server 2017](deprecated-database-engine-features-in-sql-server-2017.md)
77+
- [Deprecated database engine features in SQL Server 2016](../database-engine/deprecated-database-engine-features-in-sql-server-2016.md)
78+
- [Breaking changes to database engine features in SQL Server 2019](breaking-changes-to-database-engine-features-in-sql-server-version-15.md)
79+
- [Breaking changes to database engine features in SQL Server 2017](breaking-changes-to-database-engine-features-in-sql-server-2017.md)
80+
- [Breaking changes to database engine features in SQL Server 2016](breaking-changes-to-database-engine-features-in-sql-server-2016.md)
81+
- [Deprecated features in SQL Server replication](../relational-databases/replication/deprecated-features-in-sql-server-replication.md)

‎docs/database-engine/sql-server-database-engine-backward-compatibility.md‎

Lines changed: 0 additions & 31 deletions
This file was deleted.

‎docs/sql-server/editions-and-components-of-sql-server-version-15.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -170,7 +170,7 @@ The Developer edition continues to support only 1 client for [[!INCLUDE[ssNoVers
170170

171171
<sup>2</sup> On Enterprise Edition, the number of nodes is the operating system maximum. On Standard edition there is support for two nodes.
172172

173-
<sup>3</sup> On Enterprise Edition, provides support for up to 8 secondary replicas - including 2 synchronous secondary replicas.
173+
<sup>3</sup> On Enterprise Edition, provides support for up to 8 secondary replicas - including 5 synchronous secondary replicas.
174174

175175
<sup>4</sup> Standard Edition supports basic availability groups. A basic availability group supports two replicas, with one database. For more information about basic availability groups, see [Basic Availability Groups](../database-engine/availability-groups/windows/basic-availability-groups-always-on-availability-groups.md).
176176

‎docs/ssms/download-sql-server-management-studio-ssms.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -38,7 +38,7 @@ SSMS is free!
3838

3939
## Download SSMS
4040

41-
[Download](https://aka.ms/sssmsfullsetup) the latest release of SSMS.
41+
[Download](https://aka.ms/ssmsfullsetup) the latest release of SSMS.
4242

4343
SSMS 18.4 is the latest general availability (GA) version of SSMS. If you have a previous GA version of SSMS 18 installed, installing SSMS 18.4 upgrades it to 18.4. If you have an older *preview* version of SSMS 18.x installed, you must uninstall it before installing SSMS 18.4.
4444

@@ -79,7 +79,7 @@ SQL Server Management Studio 18.4:
7979
| SMO/Scripting | [SQL Assessment API](../sql-assessment-api/sql-assessment-api-overview.md) - Added 50 assessment rules (see details on GitHub). |
8080
| SMO/Scripting | [SQL Assessment API](../sql-assessment-api/sql-assessment-api-overview.md) - Added base math expressions and comparisons to rules conditions. |
8181
| SMO/Scripting | [SQL Assessment API](../sql-assessment-api/sql-assessment-api-overview.md) - Added support for RegisteredServer object. |
82-
| SMO/Scripting | [SQL Assessment API](../sql-assessment-api/sql-assessment-api-overview.md) - Updated way how rules are stored in the JSON format and also updated the mechanism of applying overrides/customizations. |
82+
| SMO/Scripting | [SQL Assessment API](../sql-assessment-api/sql-assessment-api-overview.md) - Updated how rules are stored in the JSON format and also updated the mechanism of applying overrides/customizations. |
8383
| SMO/Scripting | [SQL Assessment API](../sql-assessment-api/sql-assessment-api-overview.md) - Updated rules to support SQL on Linux. |
8484
| SMO/Scripting | [SQL Assessment API](../sql-assessment-api/sql-assessment-api-overview.md) - Updated the ruleset JSON format and added SCHEMA version. |
8585
| SMO/Scripting | [SQL Assessment API](../sql-assessment-api/sql-assessment-api-overview.md) - Updated cmdlets output to improve readability of recommendations. |

0 commit comments

Comments
 (0)