As a database developer or administrator, it’s unlikely that you’ll work with only one platform.
It’s quite useful to have one single tool to handle multiple different database platforms –that’s the ambition of DbVisualizer.
Let’s assume you’re a database administrator who works on a migration project moving from Oracle to EDB Postgres and Exasol.
The goal might be to replace the corporate Oracle database landscape, moving the online transaction processing (OLTP) part to EDB Postgres and the data warehousing (DWH)/analytics part to Exasol.
Instead of having to switch constantly between, say, SQL Developer, psql and EXAplus, it would be more efficient to use DbVisualizer for all three.
I created one connection for each of the three databases for this demo:
Now let’s see if the Oracle statements also work in EDB Postgres and Exasol:
And they do – for all three. The convenient thing is that you only need to select the database connection from the drop-down while leaving the statement unchanged. No need to copy and paste even.
But what about schemas and tables?
In EDB, you therefore need to create a schema:
In Exasol, the schema and table can be created in the same way:
Note that the data types got silently translated into the proper Exasol versions:
There’s no DBA_TABLES in Exasol, though:
Of course, there’s much more to check and test during a migration, but this gives you an idea how a universal SQL client like DbVisualizer might help your project.