Edit

Connect to appliance nodes in Analytics Platform System

  • Article

This article explains the various ways to connect to each node in the Analytics Platform System (PDW) appliance.

Connect with Hadoop

Before using Hadoop with Analytics Platform System (PDW), ask your appliance administrator to install the Java Runtime Environment onto SQL Server PDW. For instructions, see Configure PolyBase Connectivity to External Data (Analytics Platform System) in the Appliance Operations Guide.

Connect to appliance nodes

Each of the appliance nodes is accessed directly only under specific usage scenarios and by specific user types. The following table lists each appliance node and the scenarios under which users will connect directly to that node.

Warning

Changing database or table settings on Control or Compute nodes without explicit consent of the Product Team or APS Customer Support Team might render your APS appliance out of support.

Node Access Scenarios
Control node Use a web browser to access the Admin Console, which runs on the Control node. For more information, see Monitor the Appliance by Using the Admin Console (Analytics Platform System).

All client applications and tools connect to the Control node, regardless of whether the connection is using Ethernet or InfiniBand.

To configure an Ethernet connection to the Control node, use the Control node Cluster IP address and port 17001. For example, "192.168.0.1,17001".

To configure an InfiniBand connection to the Control node, use appliance_domain-SQLCTL01 and port 17001. By using appliance_domain-SQLCTL01, the appliance DNS server will connect your server to the active InfiniBand network. To configure your non-appliance server to use this, see Configure InfiniBand Network Adapters.

The appliance administrator connects to the Control node to perform management operations. For example, the appliance administrator performs the following operations from the Control node:

Configure Analytics Platform System with the dwconfig.exe configuration tool.
Compute node Compute node connections are directed by the Control node. The IP addresses of Compute nodes are never entered into application commands as parameters.

For loading, backup, Remote Table Copy, and Hadoop, SQL Server PDW does send or receive data directly in parallel between the Compute nodes and the non-appliance nodes or servers. These applications connect with SQL Server PDW by connecting to the Control node, and then the Control node directs SQL Server PDW to establish communication between the Compute nodes and the non-appliance server.

For example, these data transfer operations happen in parallel with direct connections to the Compute nodes:

Loading from the loading server to SQL Server PDW.

Backing up a database from SQL Server PDW to the backup server.

Restoring a database from the backup server to SQL Server PDW.

Querying Hadoop data from SQL Server PDW.

Exporting data from SQL Server PDW to an external Hadoop table.

Copying a SQL Server PDW table to a remote SMP SQL Server database.

Connect to the Ethernet and InfiniBand Networks

Remote servers can connect through either the appliance InfiniBand network or through the Ethernet network. For performance reasons, loading servers, backup servers, and servers receiving data via CREATE REMOTE TABLE AS SELECT statements, usually transfer data through the appliance InfiniBand network.

You can configure non-appliance servers to belong to your own customer workgroup or domain, and then use your own customer network to connect to those servers and transfer data to them. Also, non-appliance servers connected to the appliance InfiniBand have the option to transfer data to each other over the appliance InfiniBand network; be careful with this because it can slow the performance of SQL Server PDW.

For example, this statement adds network credentials for performing backups through InfiniBand to a backup server that has an InfiniBand IP address 192.168.0.1. The appliance domain is mypdw, and the statement is performed from the backup server. Before running this statement, you need to fill in your own parameters.

sqlcmd -S "mypdw-sqlctl01,17001" -U sa -P password -I -Q "exec sp_pdw_add_network_credentials '192.168.0.1', 'mypdw\Administrator', 'password'"

For example, a loading command will start with the following:

dwloader -S mypdw-SQLCTL01

Related content