Netherlands: Software

Introductie van Micorosoft SQL Server 2016

Issue link:

Contents of this Issue


Page 99 of 212

87 C H A P T E R 5 | Broader data access PolyBase PolyBase was introduced in SQL Server 2014 as an interface exclusively for Microsoft Analytics Platform System (APS; formerly known as Parallel Data Warehouse), with which you could access data stored in Hadoop Distributed File System (HDFS) by using SQL syntax in queries. In SQL Server 2016, you can now use PolyBase to query data in Hadoop or Azure Blob Storage and combine the results with relational data stored in SQL Server. To achieve optimal performance, PolyBase can dynamically create columnstore tables, parallelize data extraction from Hadoop and Azure sources, or push computations on Hadoop-based data to Hadoop clusters as necessary. After you install the PolyBase service and configure PolyBase data objects, your users and applications can access data from nonrelational sources without any special knowledge about Hadoop or blob storage. Installing PolyBase You can install only one instance of PolyBase on a single server, which must also have a SQL Server instance installed because the PolyBase installation process adds the following three databases: DWConfiguration, DWDiagnostics, and DWQueue. The installation process also adds the PolyBase engine service and PolyBase data movement service to the server. Before you can install PolyBase, your computer must meet the following requirements: Installed software: Microsoft .NET Framework 4.5 and Oracle Java SE RunTime Environment (JRE) version 7.51 or higher (64-bit) Minimum memory: 4 GB Minimum hard-disk space: 2 GB TCP/IP connectivity enabled To install PolyBase by using the SQL Server Installation Wizard, select PolyBase Query Service For External Data on the Feature Selection page. Then, on the Server Configuration page, you must configure the SQL Server PolyBase engine service and the SQL Server PolyBase data movement service to run under the same account. (If you create a PolyBase scale-out group, you must use the same service account across all instances.) Next, on the PolyBase Configuration page, you specify whether your SQL Server instance is a standalone PolyBase instance or part of a PolyBase scale-out group. As we describe later in this chapter, when you configure a PolyBase scale-out group, you specify whether the current instance is a head node or a compute node. Last, you define a range with a minimum of six ports to allocate to PolyBase. Note The scale-out installation process automatically opens the firewall to allow incoming connections to the database engine, the PolyBase engine, the PolyBase data movement service, and SQL Browser. It also configures the firewall to allow incoming connections from other nodes in the scale-out group. If the Firewall service is not running during PolyBase installation, this step fails. In that case, you can start the Firewall service and enable the firewall rules described at "PolyBase Installation," You can also install PolyBase from a command-prompt window by using a script such as the one shown in Example 5-26, using the following parameters specific to PolyBase: /FEATURES Identifies the features to install. If the database engine is already installed, specify PolyBase only. Otherwise, you must also include SQLEngine as a value. /PBSCALEOUT Specifies whether the instance to be installed is part of a scale-out group, with TRUE or FALSE as valid values.

Articles in this issue

Links on this page

Archives of this issue

view archives of Netherlands: Software - Introductie van Micorosoft SQL Server 2016