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/analytics-platform-system/pdw-certificate-provisioning.md
+26-24Lines changed: 26 additions & 24 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,23 +4,25 @@ description: The PDW Certificate Provisioning page of the Analytics Platform Sys
4
4
author: charlesfeddersen
5
5
ms.author: charlesf
6
6
ms.reviewer: martinle
7
-
ms.date: 04/17/2018
7
+
ms.date: 12/04/2023
8
8
ms.service: sql
9
9
ms.subservice: data-warehouse
10
-
ms.topic: conceptual
10
+
ms.topic: how-to
11
11
---
12
12
13
-
# PDW certificate provisioning - Analytics Platform System
13
+
# PDW certificate provisioning - Analytics Platform System (PDW)
14
14
The **PDW Certificate Provisioning** page of the Analytics Platform System **Configuration Manager** imports or removes the certificate used by the PDW region. Using, a certificate to encrypt connections can help secure communication to the Control node through SQL Server clients, tools that use the SQL Server PDW drivers, the [Admin Console](monitor-the-appliance-by-using-the-admin-console.md), and Integration Services loads.
15
+
16
+
Using, a certificate to encrypt connections can help secure communication to the Control node through SQL Server clients, tools that use the SQL Server PDW drivers, the [Admin Console](monitor-the-appliance-by-using-the-admin-console.md), and Integration Services loads.
15
17
16
-
## Prerequisites
18
+
## Prerequisites
17
19
Before installing the certificate, do the following:
18
20
19
-
1.Obtain a secure certificate. If you need more information about how to obtain a secure certificate, contact Microsoft Support.
21
+
1. Obtain a secure certificate. If you need more information about how to obtain a secure certificate, contact Microsoft Support.
20
22
21
-
2. Save the certificate to the Control node in a password-protected PFX file.
23
+
1. Save the certificate to the Control node in a password-protected PFX file.
22
24
23
-
## For Security Reasons, Obtain a Trusted Certificate
25
+
## For security reasons, obtain a trusted certificate
24
26
SQL Server PDW supports using a certificate to encrypt connections to the Control node; including connections to the **Admin Console**.
25
27
26
28
By default, the **Admin Console** includes a self-signed certificate that provides privacy, but not server authentication. This can leave communications vulnerable to a man-in-the-middle attack. When a user connects to the Admin Console by using the self-signed certificate, Internet Explorer returns the error: "There is a problem with this website's security certificate".
@@ -34,41 +36,41 @@ The certification path must contain the fully qualified domain name that maps to
34
36
35
37
Use the Analytics Platform System**Configuration Manager** to add or remove the trusted certificate. Directly using the Microsoft Windows HTTP Services Certificate Configuration Tool (**winHttpCertCfg.exe**) to manage the certificate is unsupported.
36
38
37
-
## Import or Remove the Certificate
39
+
## Import or Remove the Certificate
38
40
The following instructions show how to import or remove the appliance certificate.
39
41
40
42
> [!WARNING]
41
43
> To renew an expired certificate you must remove the existing certificate BEFORE importing the new one.
42
44
43
-
### To importthecertificate
45
+
### <aid="to-import-the-certificate"></a> Import the certificate
44
46
45
-
1.Launch the **Configuration Manager**. For more information, see [Launch the Configuration Manager (Analytics Platform System)](launch-the-configuration-manager.md).
47
+
1. Launch the **Configuration Manager**. For more information, see [Launch the Configuration Manager (Analytics Platform System)](launch-the-configuration-manager.md).
46
48
47
-
2.In the left pane of the **Configuration Manager**, expand **Parallel Data Warehouse Topology**, and then click**Certificates**.
49
+
1.In the left pane of the **Configuration Manager**, expand **Parallel Data Warehouse Topology**, and then select**Certificates**.
48
50
49
-
3.Select **Import a certificate and configure the appliance to use it**, and then click**Browse** to browse to and select the certificate file.
51
+
1.Select **Import a certificate and configure the appliance to use it**, and then select**Browse** to browse to and select the certificate file.
50
52
51
-
4. Enter the password for the certificate in the **Password** field.
53
+
1. Enter the password for the certificate in the **Password** field.
52
54
53
-
5. Click**Apply** to configure the certificate for the appliance.
55
+
1. Select**Apply** to configure the certificate for the appliance.
54
56
55
57
SQL Server PDW will not encrypt current connection by using the imported certificate, but will use the certificate for new connections.
56
58
57
-
### To removethe previously imported certificate
59
+
### <aid="to-remove-the-previously-imported-certificate"></a> Remove the previously imported certificate
58
60
59
-
1.Launch the **Configuration Manager**. For more information, see [Launch the Configuration Manager (Analytics Platform System)](launch-the-configuration-manager.md).
61
+
1. Launch the **Configuration Manager**. For more information, see [Launch the Configuration Manager (Analytics Platform System)](launch-the-configuration-manager.md).
60
62
61
-
2.In the left pane of the **Configuration Manager**, expand **Parallel Data Warehouse Topology**, and then click**Certificates**.
63
+
1.In the left pane of the **Configuration Manager**, expand **Parallel Data Warehouse Topology**, and then select**Certificates**.
62
64
63
-
3. Select **Remove any certificate provisioned in the appliance**.
65
+
1. Select **Remove any certificate provisioned in the appliance**.
64
66
65
-
4. Click**Apply** to remove the previously imported certificate from the appliance.
67
+
1. Select**Apply** to remove the previously imported certificate from the appliance.
66
68
67
69
SQL Server PDW will continue to encrypt current connections, but will not use the removed certificate for new connections.
:::image type="content" source="./media/pdw-certificate-provisioning/SQL_Server_PDW_DWConfig_ApplPDWCert.png" alt-text="A screenshot of the Microsoft Analytics Platform System Configuration Manager, showing the Certificates page.":::
74
72
73
+
## Related content
74
+
75
+
-[Launch the Configuration Manager in Analytics Platform System](launch-the-configuration-manager.md)
Copy file name to clipboardExpand all lines: docs/analytics-platform-system/pdw-firewall-configuration.md
+19-15Lines changed: 19 additions & 15 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,28 +4,28 @@ description: The firewall page of the SQL Server PDW Configuration Manager enabl
4
4
author: charlesfeddersen
5
5
ms.author: charlesf
6
6
ms.reviewer: martinle
7
-
ms.date: 04/17/2018
7
+
ms.date: 12/04/2023
8
8
ms.service: sql
9
9
ms.subservice: data-warehouse
10
-
ms.topic: conceptual
10
+
ms.topic: how-to
11
11
---
12
-
# Parallel Data Warehouse firewall configuration in Analytics Platform System
12
+
# Parallel Data Warehouse firewall configuration in Analytics Platform System (PDW)
13
13
14
14
The **Firewall** page of the SQL Server PDW Configuration Manager enables you to enable or disable firewall rules that allow or prevent access to specific ports on the Analytics Platform System appliance.
15
15
16
-
## To manageports and firewall rules for appliance nodes
16
+
## <aid="to-manage-ports-and-firewall-rules-for-appliance-nodes"></a> Manage ports and firewall rules for appliance nodes
17
17
18
-
1.Launch the Configuration Manager. For more information, see [Launch the Configuration Manager (Analytics Platform System)](launch-the-configuration-manager.md).
18
+
1. Launch the Configuration Manager. For more information, see [Launch the Configuration Manager (Analytics Platform System)](launch-the-configuration-manager.md).
19
19
20
-
2.In the left pane of the Configuration Manager, expand **Parallel Data Warehouse Topology**, and then click**Firewall**.
20
+
1.In the left pane of the Configuration Manager, expand **Parallel Data Warehouse Topology**, and then select**Firewall**.
21
21
22
-
3. Locate the port or firewall rule to update in the configuration list, and then select or clear the box next to that item. Only SQL Server PDW admin-configurable options are shown in this list, including opening and closing ports on externally facing nodes.
22
+
1. Locate the port or firewall rule to update in the configuration list, and then select or clear the box next to that item. Only SQL Server PDW admin-configurable options are shown in this list, including opening and closing ports on externally facing nodes.
:::image type="content" source="./media/pdw-firewall-configuration/SQL_Server_PDW_DWConfig_ApplPDWFirewall.png" alt-text="Screenshot of the Microsoft Analytics Platform System Configuration Manager, showing the Firewall page.":::
27
27
28
-
## External Ports
28
+
## External Ports
29
29
The following ports are opened for client connections coming from outside of PDW.
30
30
31
31
|Purpose|Port #|Nodes|
@@ -37,10 +37,10 @@ The following ports are opened for client connections coming from outside of PDW
37
37
|dwloader BinaryLoaderDataChannel|16551|CMP|
38
38
|SSL encrypted connections (For internal communications, to access the Admin Console)|443|All nodes|
39
39
|SQL Server PDW Load Control Flow - Windows Credentials|8002|CTL|
40
-
|_Kerberos|88|AD01 and AD02,|
40
+
|_Kerberos|88|AD01 and AD02|
41
41
|_ldap|389|AD01 and AD02|
42
42
43
-
## Internal Ports
43
+
## Internal Ports
44
44
The following ports are used by PDW for internal communication, but are not opened for connections coming from outside of the PDW appliance.
45
45
46
46
|Purpose|Port #|Nodes|
@@ -54,9 +54,13 @@ The following ports are used by PDW for internal communication, but are not open
54
54
|SQL Server port ranges (TDS)|1433, 1500-1508|CTL, CMP|
55
55
56
56
> [!NOTE]
57
-
> Creating external tables or external data sources uses TCP port 8020 by default. These statements can be configured to use other ports instead. The Hortonworks JOB_TRACKER_LOCATION default port is 50300. Integrating with other systems and tools may require additional ports.
57
+
> Creating external tables or external data sources uses TCP port 8020 by default. These statements can be configured to use other ports instead. The Hortonworks JOB_TRACKER_LOCATION default port is 50300. Integrating with other systems and tools might require additional ports.
description: Parallel Data Warehouse (PDW) services status for Analytics Platform System.
2
+
title: Analytics Platform System (PDW) services status
3
+
description: Analytics Platform System (PDW) services status for Analytics Platform System.
4
4
author: charlesfeddersen
5
5
ms.author: charlesf
6
6
ms.reviewer: martinle
7
-
ms.date: 04/17/2018
7
+
ms.date: 12/04/2023
8
8
ms.service: sql
9
9
ms.subservice: data-warehouse
10
-
ms.topic: conceptual
10
+
ms.topic: how-to
11
11
---
12
12
13
-
# Parallel Data Warehouse services status for Analytics Platform System
14
-
The Parallel Data Warehouse **Services Status** page in the Microsoft Analytics Platform System Configuration Manager shows the current status of all SQL Server PDW services, and provides the ability to stop and start the PDW services. This is the only supported method for starting and stopping the PDW services. Note that individual components or services cannot be started independently.
13
+
# Parallel Data Warehouse services status for Analytics Platform System (PDW)
14
+
The Parallel Data Warehouse **Services Status** page in the Microsoft Analytics Platform System Configuration Manager shows the current status of all SQL Server PDW services, and provides the ability to stop and start the PDW services. This is the only supported method for starting and stopping the PDW services. Individual components or services cannot be started independently.
15
15
16
-
#### To startor stop the appliance services
16
+
#### <aid="to-start-or-stop-the-appliance-services"></a> Start or stop the appliance services
17
17
18
-
1.To start the appliance services, click**Start Appliance**.
18
+
1. To start the appliance services, select**Start Appliance**.
19
19
20
-
2.To stop the appliance services, click**Stop Appliance**.
20
+
1.To stop the appliance services, select**Stop Appliance**.
21
21
22
-
It is not necessary to click**Apply** when starting and stopping the appliance services by using **Start Appliance** and **Stop Appliance**.
22
+
It is not necessary to select**Apply** when starting and stopping the appliance services by using **Start Appliance** and **Stop Appliance**.
:::image type="content" source="./media/pdw-services-status/SQL_Server_PDW_DWConfig_ApplPDWServices.png" alt-text="A screenshot of the Microsoft Analytics Platform System Configuration Manager, showing the Services Status page.":::
25
25
26
26
> [!NOTE]
27
27
> Stopping the PDW Region also stops the PDW agent (sqldwagent) on the nodes. The PDW agent requires the PDW control node to report health monitoring.
28
28
29
-
## See Also
30
-
[Power the APS Appliance On or Off (Analytics Platform System)](power-the-aps-appliance-on-or-off.md)
31
-
29
+
## Related content
30
+
31
+
-[Power the appliance on or off for Analytics Platform System](power-the-aps-appliance-on-or-off.md)
Displays name and network information about the SQL Server PDW components. Use the **Appliance Topology Network Configuration** page to change the network IP Addresses.
15
15
16
-
![DWConfig PDW top menu](./media/pdw-topology/SQL_Server_PDW_DWConfig_PDWTop.png"SQL_Server_PDW_DWConfig_PDWTop")
17
-
18
-
## See Also
19
-
[Launch the Configuration Manager (Analytics Platform System)](launch-the-configuration-manager.md)
20
-
16
+
:::image type="content" source="./media/pdw-topology/SQL_Server_PDW_DWConfig_PDWTop.png" alt-text="Screenshot of the Microsoft Analytics Platform System Configuration Manager, showing the Parallel Data Warehouse topology page.":::
17
+
18
+
## Related content
19
+
20
+
-[Launch the Configuration Manager in Analytics Platform System](launch-the-configuration-manager.md)
Copy file name to clipboardExpand all lines: docs/analytics-platform-system/polybase-configure-azure-blob-storage.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
@@ -4,10 +4,10 @@ description: Explains how to use PolyBase on a Parallel Data Warehouse (APS) to
4
4
author: charlesfeddersen
5
5
ms.author: charlesf
6
6
ms.reviewer: martinle
7
-
ms.date: 04/17/2018
7
+
ms.date: 12/04/2023
8
8
ms.service: sql
9
9
ms.subservice: data-warehouse
10
-
ms.topic: conceptual
10
+
ms.topic: how-to
11
11
---
12
12
# Configure PolyBase to access external data in Azure Blob Storage
13
13
@@ -38,7 +38,7 @@ First, configure APS to use Azure Blob Storage.
38
38
GO
39
39
```
40
40
41
-
2. Restart APS Region using Service Status page on [Appliance Configuration Manager](launch-the-configuration-manager.md).
41
+
1. Restart APS Region using Service Status page on [Appliance Configuration Manager](launch-the-configuration-manager.md).
42
42
43
43
## Configure an external table
44
44
@@ -115,7 +115,7 @@ There are three functions that PolyBase is suited for:
115
115
116
116
The following queries provide example with fictional car sensor data.
117
117
118
-
### Ad hoc queries
118
+
### Ad hoc queries
119
119
120
120
The following ad hoc query joins relational with data in Azure Blob Storage. It selects customers who drive faster than 35 mph, joining structured customer data stored in SQL Server with car sensor data stored in Azure Blob Storage.
121
121
@@ -127,7 +127,7 @@ WHERE Insured_Customers.CustomerKey = CarSensor_Data.CustomerKey and CarSensor_D
127
127
ORDER BYCarSensor_Data.SpeedDESC
128
128
```
129
129
130
-
### Importing data
130
+
### <aid="importing-data"></a> Import data
131
131
132
132
The following query imports external data into APS. This example imports data for fast drivers into APS to do more in-depth analysis. To improve performance, it leverages Columnstore technology in APS.
133
133
@@ -146,7 +146,7 @@ from Insured_Customers INNER JOIN
The following query exports data from APS to Azure Blob Storage. It can be used to archive relational data to Azure Blob Storage while still be able to query it.
152
152
@@ -164,13 +164,13 @@ ON (T1.CustomerKey = T2.CustomerKey)
164
164
WHERET2.YearMeasured=2009andT2.Speed>40;
165
165
```
166
166
167
-
## View PolyBase objects in SSDT
167
+
## View PolyBase objects in SSDT
168
168
169
-
In SQL Server Data Tools, external tables are displayed in a separate folder **External Tables**. External data sources and external file formats are in subfolders under **External Resources**.
169
+
In SQL Server Data Tools (SSDT), external tables are displayed in a separate folder **External Tables**. External data sources and external file formats are in subfolders under **External Resources**.
170
170
171
-
171
+
:::image type="content" source="media/polybase/external-tables-datasource.png" alt-text="A screenshot of PolyBase objects in the object explorer of SSDT.":::
172
172
173
-
## Next steps
174
-
175
-
For more information about PolyBase, see the [What is PolyBase?](../relational-databases/polybase/polybase-guide.md).
173
+
## Next step
176
174
175
+
> [!div class="nextstepaction"]
176
+
> [Introducing data virtualization with PolyBase](../relational-databases/polybase/polybase-guide.md)
0 commit comments