This article talks about how to install SQL Server 2017 polybase post upgrading from SQL Server 2014 and troubleshooting polybase installation rule failures.
For more details and limitations go to
Polybase is introduced in SQL Server 2016.So, post upgrading you have to install polybase as a fresh feature installation to an existing upgraded SQL Server instance.
Polybase Require Oracle JRE 7 or later. If you don’t have Oracle JRE installed SQL Server 2017 setup feature rule will fail as shown below
To resolve the above error , Download and install Version 8 of the JRE which is compatible with the SQL Server 2017 installer. (Version 9 of the JRE is not compatible with SQL Server 2017 installer, SQL Server 2017 installer cannot detect version 9 of the JRE as Oracle has changed windows registry key names). If you have installed version 9 of the JRE follow the link to fix the issue. https://support.microsoft.com/en-in/help/4077899/fix-polybase-is-not-installed-when-you-install-sql-server-2017.
Once Jave runtime is installed successfully, rerun the feature rules.
After running the feature rules successfully, Configure the polybase configuration.
Choose your option and specify port range with at least six ports. SQL Server setup will allocate the first six available ports from the range.
SQL Server PolyBase setup creates the following firewall rules on the machine.
- SQL Server PolyBase – Database Engine – <SQLServerInstanceName> (TCP-In)
- SQL Server PolyBase – PolyBase Services – <SQLServerInstanceName> (TCP-In)
SQL Server PolyBase – SQL Browser – (UDP-In)
At installation, if you choose to use the SQL Server instance as part of a PolyBase Scale-out Group, these rules are enabled and the firewall is opened to allow incoming connections to the SQL Server Database Engine, SQL Server PolyBase Engine, SQL Server PolyBase Data Movement service and SQL Browser. However, if the Firewall service on the machine is not running during installation, SQL Server setup would fail to enable these rules. In that case, you must start the Firewall service on the machine and enable these rules post-installation.
Once Polybase feature is installed successfully. Check SQL Server Configuration Manager for Service Status
Check SQL Server Error log with filter as “Polybase”
You can also check the polybase data management service status using sys.dm_exec_dms_services dmv
SELECT * FROM sys.dm_exec_dms_services
For Polybase Installation confirmation,run the following command.
If PolyBase is installed, returns 1; otherwise, 0.
Post installation notes
PolyBase installs three user databases, DWConfiguration, DWDiagnostics, and DWQueue. These are for PolyBase use and should not be altered or deleted.