Oops, we did it again 🙂 Exasol just won the TPC-H benchmark in the categories 3 TB and 10 TB database sizes.
The TPC-H benchmark is designed for decision support systems respectively for analytical workloads.
That proves again that Exasol really is the fastest analytical database in the world!
We’re leading both in pure performance and price/performance.
To quote our engineers who worked on that benchmark:
“The results are beaten in performance only by our own historical results on much more hardware, in price-performance we are the best ever.
Our performance per CPU core improved significantly compared to 2014.”
As a Database Developer or Database Administrator, it becomes increasingly unlikely that you will work with only one platform.
It’s quite useful to have one single tool to handle multiple different database platforms. And that’s exactly the ambition of DbVisualizer.
As a hypothetical scenario, let’s assume you are a database admin who works on a project to migrate from Oracle to EDB Postgres and Exasol.
The goal might be to replace the corporate Oracle database landscape, moving the OLTP part to EDB Postgres and the DWH / Analytics part to Exasol.
Instead of having to switch constantly between say SQL Developer, psql and EXAplus, a more efficient approach would be using DbVisualizer for all three.
I created one connection for each of the three databases here for my demo:Now let’s see if statements I do in Oracle also work in EDB Postgres and in Exasol:
Works the same for all three! The convenient thing here is that I just had to select the Database Connection from the pull down menu while leaving the statement as it is. No need to copy & paste even.
What about schemas and tables?
In EDB, I need to create a schema accordingly:
In Exasol, schema and table can be created in the same way:
Notice that the data types got silently translated into the proper Exasol data types:
There is no DBA_TABLES in Exasol, though:
Of course, there’s much more to check and test upon migration, but I think you got an idea how a universal SQL Client like DbVisualizer might help for such purposes.
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]
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 🙂