Sql-server – Polybase with SQL Server 2019 on Linux or Containers

containerspolybasesql serverUbuntu

I would like to install SQL Server 2019 on Linux either a full Linux server (Ubuntu 18.04) or on a Docker container with Polybase. Installing MSSQL 2019 on a Linux Server or a container is relatively easy. It's the Polybase bit that I cannot figure out.

Using the instructions at this Microsoft Docs site: https://docs.microsoft.com/en-us/sql/relational-databases/polybase/polybase-linux-setup?view=sql-server-ver15

There is a reference to install Polybase on Ubuntu, which should be applicable in both cases (server or container). When I attempted to install the Polybase packages on an Ubuntu server I got this result:

sudo apt-get install mssql-server-polybase

Installed without any issue

sudo apt-get install mssql-server-polybase-hadoop

The following packages have unmet dependencies: mssql-server-polybase-hadoop : Depends: mssql-zulu-jre-11 but it is not installable E: Unable to correct problems, you have held broken packages.

I could not find a solution to installing the package mssql-zulu-jre-11 on a Linux Server.

In a container, I logged in as a Root user and attempted the commands above:

apt-get install mssql-server-polybase

E: Unable to locate package mssql-server-polybase

I did verify that within the container the Linux instance has the correct sources for apt to find this package. I am completely confused as to how to get Polybase running with SQL Server 2019 on Linux. Have any of your had success? Any help would be greatly appreciated!

Best Answer

After a lot of trial and error and a lot of research, I found a solution.

I tried both Ubuntu 16.04 and Ubuntu 18.04. This installation approach works for both, but I only was able to get Polybase to work under Ubuntu 18.04.

I performed a fresh install of Ubuntu and SQL Server. As with every attempt, everything went well except the installation of the mssql-server-polybase-hadoop package. It failed on attempting to find and install the mssql-zulu-jre-11 package.

However, I downloaded the .deb package and manually installed it from these locations:

Ubuntu 16.04: https://packages.microsoft.com/ubuntu/16.04/prod/pool/main/m/mssql-zulu-jre-11/mssql-zulu-jre-11_11.43.56-1_amd64.deb

Ubuntu 18.04: https://packages.microsoft.com/ubuntu/18.04/prod/pool/main/m/mssql-zulu-jre-11/mssql-zulu-jre-11_11.43.56-1_amd64.deb

After installing it with dpkg -i, I was able to then install the mssql-server-polybase-hadoop package.

This process allowed me to configure and use Polybase. (Only with Ubuntu 18.04)

Related Solutions

Postgresql – Installing and configuring postgresql 9.3 on ubuntu 13.10 using puppet

Dunno if it was true when you wrote your question, but the puppetlabs/postgresql module does some pretty clever stuff with versions that are not standard for your OS distro, including installing the required repository.

Snippets from my config:

In one of my puppet classes I call:

    class { 'postgresql::globals':
      encoding => hiera('postgresql::globals::encoding', 'UTF8'),
      locale => hiera('postgresql::globals::locale', 'C'),
      manage_package_repo => hiera('postgresql::globals::manage_package_repo', false),
      version => hiera('postgresql::globals::version', undef),
      notify => Class['postgresql::server', 'postgresql::client'],
    }

and in my hiera config data I have:

postgresql::globals::version: "9.3"
postgresql::globals::manage_package_repo: true

Using hiera like this is optional of course, but it gives you a nice way to use different versions on different hosts. On later versions of puppet (at least 3.x) you can override postgresql::globals variables without needing that to be part of how you call the package.

You won't need to do stuff from source here, but if you did, I'd recommend that you should build your own package rather than try to automate the build process through puppet. Avoid it as far as possible though, since it sets you up to do ongoing maintenance of that package.

Mysql – Workbench freezes on connecting after Ubuntu 18.04 upgrade

After further investigation I managed to resolve this issue, it seems that after the upgrade my settings must've got screwed up. The connection that wasn't even the one I was attempting to use which was a bit strange.

I went into the paths that mentioned in the log:

11:39:08 [WRN][            grt]: /usr/share/mysql-workbench/modules/data/mysql_rdbms_info.xml:1401: link 'om.mysql.rdbms.mysql.driver.native_sshtun' <object > key=owner could not be resolved
11:39:08 [WRN][            grt]: /home/<REPLACED USERNAME>/.mysql/workbench/connections.xml:27: link '6d8ecd74-acad-11e8-9c35-408d5cdbf11f' <object GrtObject> key=owner could not be resolved

And deleted the 'value' tags as well as the connection that was throwing the error and restarted mysql workbench. After the restart some of the connections I had setup were gone (which I can just recreate) but it seems that I can connect fine now.

Best Answer

Related Solutions

Postgresql – Installing and configuring postgresql 9.3 on ubuntu 13.10 using puppet

Mysql – Workbench freezes on connecting after Ubuntu 18.04 upgrade

Related Question