


- SQL SERVER 2017 DEVELOPER EDITION FAILED TO INSTALL INSTALL
- SQL SERVER 2017 DEVELOPER EDITION FAILED TO INSTALL MANUAL
Something must have gone wrong, but what! However, the two PolyBase services are still in a Starting state. We see that the SQL Server service, ( MSSQLSERVER), is in Running state. What we see in Figure 4 is a view of services a couple of minutes after the installation.
SQL SERVER 2017 DEVELOPER EDITION FAILED TO INSTALL MANUAL
Cool! Problemīut has the installation succeeded? What usually I do after a SQL installation is to go to Services and change properties for the various SQL services, (automatic startup to manual startup, etc.). We see in Figure 3 how all components are green which indicates that the installation has succeeded. I click on from there and eventually the installation finishes: After clicking on from there passing Feature Rules, and Instance Configuration we get to PolyBase Configuration:Īs we see from Figure 2 I choose a standalone PolyBase-enabled instance. In Figure 1 we see how I chose both the PolyBase Query Service as well as the Java connector for HDFS data sources. In both cases, you select it during feature selection:
SQL SERVER 2017 DEVELOPER EDITION FAILED TO INSTALL INSTALL
You either install PolyBase as part of a regular installation of a SQL Server instance, or you add it after installation.
