You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/database-engine/install-windows/add-features-to-an-instance-of-sql-server-setup.md
+12-12Lines changed: 12 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,7 +12,7 @@ author: cawrites
12
12
ms.author: chadam
13
13
ms.reviewer: ""
14
14
ms.custom: ""
15
-
ms.date: 02/05/2021
15
+
ms.date: 10/04/2021
16
16
monikerRange: ">=sql-server-2016"
17
17
---
18
18
@@ -29,13 +29,11 @@ To add features to an instance of SQL Server from the command prompt, see [Insta
29
29
30
30
## Prerequisites
31
31
32
-
Before you continue, review articles in [Planning a SQL Server Installation](../../sql-server/install/planning-a-sql-server-installation.md).
32
+
Before you continue, review articles in [Planning a SQL Server Installation](../../sql-server/install/planning-a-sql-server-installation.md). Also be aware:
33
33
34
-
> [!NOTE]
35
-
> For local installations, you must run Setup as an administrator. If you install SQL Server from a remote share, you must use a domain account that has read permissions on the remote share.
36
-
37
-
> [!NOTE]
38
-
> When you add features to an instance of [!INCLUDE[ssnoversion](../../includes/ssnoversion-md.md)], the existing usage report settings are applied to the newly-added features. To change these settings, use the **SQL Server Error and Usage Reporting** tool on the SQL Server **Configuration Tools** menu.
34
+
- For local installations, you must run Setup as an administrator. If you install SQL Server from a remote share, you must use a domain account that has read permissions on the remote share.
35
+
- When you add features to an instance of [!INCLUDE[ssnoversion](../../includes/ssnoversion-md.md)], the existing usage report settings are applied to the newly added features. To change these settings, use the **SQL Server Error and Usage Reporting** tool on the SQL Server **Configuration Tools** menu.
36
+
- You cannot add features to a failover cluster instance. For example, you cannot add the PolyBase feature to an existing failover cluster instance. Similarly, removing features from a failover cluster instance is also not supported.
39
37
40
38
## Procedures
41
39
@@ -57,7 +55,7 @@ Before you continue, review articles in [Planning a SQL Server Installation](../
57
55
58
56
8. On the Feature Selection page, select the components for your installation. A description for each component group appears in the right-hand pane after you select the feature name. You can select any combination of check boxes. For more information, see [Editions and supported features of SQL Server 2017](../../sql-server/editions-and-components-of-sql-server-2017.md) and [SQL Server 2019](../../sql-server/editions-and-components-of-sql-server-version-15.md). Each component can be installed only once on a given instance of SQL Server. To install multiple components, you must install an additional instance of SQL Server.
59
57
60
-
The prerequisites for the selected features are displayed on the right-hand pane. SQL Server Setup will install the prerequisite that are not already installed during the installation step described later in this procedure.
58
+
The prerequisites for the selected features are displayed on the right-hand pane. SQL Server Setup will install the prerequisites that are not already installed during the installation step described later in this procedure.
61
59
62
60
The System Configuration Checker will verify the system state of your computer before Setup continues. Select **Next** to continue.
63
61
@@ -77,7 +75,7 @@ Before you continue, review articles in [Planning a SQL Server Installation](../
77
75
78
76
12. Use the **Server Configuration - Collation** tab to specify non-default collations for the Database Engine and Analysis Services. For more information, see [Server Configuration - Collation](./install-sql-server.md).
79
77
80
-
13. Use the Database Engine Configuration - Account Provisioning page to specify the following:
78
+
13. Use the Database Engine Configuration - Account Provisioning page to specify the following settings:
81
79
82
80
- Security Mode - Select Windows Authentication or Mixed Mode Authentication for your instance of SQL Server. If you select Mixed Mode Authentication, you must provide a strong password for the built-in SQL Server system administrator account.
83
81
@@ -96,7 +94,9 @@ Before you continue, review articles in [Planning a SQL Server Installation](../
96
94
97
95
15. Use the Database Engine Configuration - FILESTREAM page to enable FILESTREAM for your instance of SQL Server. For more information about FILESTREAM, see [Database Engine Configuration - Filestream](./install-sql-server.md). To continue, select Next.
98
96
99
-
16. Use the Analysis Services Configuration - Account Provisioning page to specify the server mode and the users or accounts that will have administrator permissions for Analysis Services. Server mode determines which memory and storage subsystems are used on the server. Different solution types run in different server modes. If you plan to run multidimensional cube databases on the server, choose the default option, Multidimensional and Data Mining server mode. Regarding administrator permissions, you must specify at least one system administrator for Analysis Services. To add the account under which SQL Server Setup is running, select **Add Current User**. To add or remove accounts from the list of system administrators, select **Add** or **Remove**, and then edit the list of users, groups, or computers that will have administrator privileges for Analysis Services. For more information about server mode and administrator permissions, see [Analysis Services Configuration - Account Provisioning](./install-sql-server.md).
97
+
16. Use the Analysis Services Configuration - Account Provisioning page to specify the server mode and the users or accounts that will have administrator permissions for Analysis Services. Server mode determines which memory and storage subsystems are used on the server. Different solution types run in different server modes. An instance of Analysis Services can support either conventional multidimensional cubes, or tabular models, but an instance cannot support both types of models. For new development, use the default option, **Tabular Mode**.
98
+
99
+
Regarding administrator permissions, you must specify at least one system administrator for Analysis Services. To add the account under which SQL Server Setup is running, select **Add Current User**. To add or remove accounts from the list of system administrators, select **Add** or **Remove**, and then edit the list of users, groups, or computers that will have administrator privileges for Analysis Services. For more information about server mode and administrator permissions, see [Analysis Services Configuration - Account Provisioning](./install-sql-server.md).
100
100
101
101
When you are finished editing the list, select **OK**. Verify the list of administrators in the configuration dialog box. When the list is complete, select **Next**.
102
102
@@ -117,7 +117,7 @@ Before you continue, review articles in [Planning a SQL Server Installation](../
117
117
118
118
20. Use the Distributed Replay Client Configuration page to specify the users you want to grant administrative permissions to for the Distributed Replay client service. Users that have administrative permissions will have unlimited access to the Distributed Replay client service.
119
119
120
-
**Controller Name** is an optional parameter, and the default value is \<*blank*>. Enter the name of the controller that the client computer will communicate with for the Distributed Replay client service. Note the following:
120
+
**Controller Name** is an optional parameter, and the default value is \<*blank*>. Enter the name of the controller that the client computer will communicate with for the Distributed Replay client service. Note the following conditions:
121
121
122
122
- If you have already set up a controller, enter the name of the controller while configuring each client.
123
123
@@ -129,7 +129,7 @@ Before you continue, review articles in [Planning a SQL Server Installation](../
129
129
130
130
To continue, select **Next**.
131
131
132
-
21. On the Error Reporting page, specify the information you would like to send to Microsoft that will help to improve SQL Server. By default, options for error reporting is enabled.
132
+
21. On the Error Reporting page, specify the information you would like to send to Microsoft that will help to improve SQL Server. By default, the option for error reporting is enabled.
133
133
134
134
22. The System Configuration Checker will run one more set of rules to validate your computer configuration with the SQL Server features you have specified.
Copy file name to clipboardExpand all lines: docs/relational-databases/polybase/polybase-installation.md
+4-3Lines changed: 4 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
---
2
2
title: "Install PolyBase on Windows"
3
3
description: Learn to install PolyBase as a single node or PolyBase scale-out group. You can use an installation wizard or a command prompt. Finally, enable PolyBase.
4
-
ms.date: 08/05/2021
4
+
ms.date: 10/04/2021
5
5
ms.prod: sql
6
6
ms.technology: polybase
7
7
ms.topic: conceptual
@@ -36,8 +36,9 @@ To install a trial version of SQL Server, go to [SQL Server evaluations](https:/
36
36
37
37
- PolyBase services require Shared Memory protocol to be enabled to function properly.
38
38
39
-
>[!NOTE]
40
-
> PolyBase can be installed on only one SQL Server instance per machine.
39
+
- PolyBase can be installed on only one SQL Server instance per machine.
40
+
41
+
- You cannot add features to a failover cluster instance after creation. For example, you cannot add the PolyBase feature to an existing failover cluster instance.
0 commit comments