Version 19.1 of SQL Developer, SQLcl, Data Modeler, and ORDS are now all available, and you can expect many posts over the next few weeks to cover all the new goodies.
Today I want to highlight some changes we made to how you define your connections.
One change you’ll see right away is a simpler connection dialog:
The name and color of the connection is up top now, and it’s hopefully less likely you’ll type your password into the username input area by accident!
Proxy User info is moved up top next to the rest of the username stuff – it’s no longer on an advanced pop up dialog.
Now about that Advanced page you still see there, I want to call out a new feature exposed there:
You can now define connections as THICK or THIN.
Previously, SQL Developer would be configured for THICK or THIN connections, application wide, via the ‘Use OCI’ preference on the Advanced page.
Just to back up a bit, your options for connecting to Oracle with our JDBC driver are:
- thin = PURE JAVA, what most people should be using
- thick = mix of Java and native compiled libraries via Oracle Client or Instant Client, required for some use cases like RADIUS authentication
And it’s totally fine to usually just go with THIN. Nothing else needed to install or configure.
There are however, some reasons you might need to go ‘thick.’ You can read all about how this works here.
But now, I can have connections in a single instance of SQL Developer going with both THIN and THICK configurations.
If we look at the connection properties for the THICK connection:
You’ll still need to go about configuring your $ORACLE_HOME or Instant Client in the Advanced Preferences page. And, I still recommend you use the TEST feature, to make sure your OCI connections will be available. The ‘show jdbc’ command ran through our script engine (F5) will also confirm your type of connection.