One of the more interesting parts of SQL Server 2019 CTP 3.2’s release notes is the relationship between Microsoft and Azul Systems. Travis Wright covers it in some detail, as well as what it means for customers.

Prior to SQL Server 2019 CTP 3.2, installing PolyBase required an installation of Oracle’s Java Runtime Environment 7 Update 51 or higher, either directly from Oracle or through OpenJDK.

Daily security patches ahoy!

If you tried to skirt the installation, you’d get an error message telling you not to pass GO and not to collect $200.

Whomp whomp.

But as of CTP 3.2, your life just got 0.85% better. There’s no more prompt about Oracle JRE 7+ on initial installation.

Not pictured: the biggest reason people avoided installing PolyBase.

Instead, there’s another prompt in the setup for Java installation.

Look, you still have to install Java. That’s why life only got 0.85% better.

Our options now are either to tell SQL Server which Java runtime to use, or let it install Azul’s Zulu OpenJDK installation of the Java Runtime Environment. This way, you can avoid any potential issues around Oracle’s licensing changes for Java SE.


One thought on “PolyBase and Azul Zulu OpenJDK

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s