Search

Top 60 Oracle Blogs

Recent comments

Why you cannot use #Oracle’s SQL Developer to connect to #Exasol

Many of our customers are using Oracle together with SQL Developer, so this question comes up regularly: Can we use SQL Developer also for Exasol?

Short answer is: Unfortunately not.

I tried myself to make that work with no success. Then I found this on Stackoverflow:

Jeff Smith: “No, that’s not supported. SQL Developer’s 3rd party JDBC connectivity is provided for one use case – migrations to Oracle Database.
There’s no support on that for Exasol DB, so there’s no connectivity support provided.
If you want a generic jdbc db client, that’s not Oracle SQL Developer.” [Highlighted by me]

https://uhesse.files.wordpress.com/2019/06/sqldeveloper.png?w=150&h=104 150w, https://uhesse.files.wordpress.com/2019/06/sqldeveloper.png?w=300&h=209 300w, https://uhesse.files.wordpress.com/2019/06/sqldeveloper.png 759w" sizes="(max-width: 620px) 100vw, 620px" />

Jeff Smith is not just someone from the internet: Besides of having a high reputation for being helpful in public forums, he’s also Oracle’s Product Manager for SQL Developer.

So that means SQL Developer doesn’t connect to Exasol because it’s not supposed to do that. It’s not so much a technical but a “political” reason behind it.

We as Exasol can’t do anything about it. You as an Oracle customer who wants this to work could request that from Oracle. But don’t hold your breath until they allow it </p />
</p></div>

    	  	<div class=