Database guides
Exasol
In-memory MPP analytics database, reached over its JSON-over-WebSocket protocol. Needs a build with the exasol feature enabled.
Exasol is an in-memory, massively-parallel analytics database. Clients talk to it with JSON messages over a WebSocket rather than a traditional wire protocol. AddisDB implements that protocol directly.
Who it is for
Exasol is chosen for speed on analytical workloads — it is consistently at the top of independent analytics benchmarks. It suits organisations with a well-defined reporting workload and the budget for an in-memory system, and is typically run as a cluster.
Set up the connection
- Note a cluster node’s host and the port — 8563 by default.
- Note the user. sys is the built-in administrator.
- Optionally note a schema to open on connect, which scopes the schema tree and lets you write unqualified table names.
- Check whether the cluster presents a self-signed certificate — most on-premise installs do.
Connect from AddisDB
- New Connection → Exasol. Port prefills to 8563 and username to sys.
- Enter the host and password, and optionally a schema in the database field.
- Leave SSL mode at require — Exasol expects TLS.
- Test, then Save.
What AddisDB gives you
Queries and the Big Data Console, the schema tree read from EXA_ALL_COLUMNS, exports, saved queries and mock data.
Exasol returns results column by column rather than row by row. AddisDB transposes them, so the grid shows what you would expect rather than a result set turned on its side.