Connect to the database¶
Run exasol info after installation to display database connection details. The deployment's
secrets.json contains the credentials needed by database clients.
See Connect to Exasol for supported drivers and client applications.
Use the built-in SQL client¶
Start an interactive SQL session:
Run one or more semicolon-separated statements without opening an interactive session:
Run statements from a file:
--command and --file are mutually exclusive. Non-interactive execution stops at the first failed
statement and exits with a non-zero status.
Select the output format¶
Use --csv for CSV output:
Use --json for machine-readable output. A non-interactive invocation writes one JSON document for
all statements, including SQL errors. An interactive exasol connect --json session writes one JSON
document per statement.
For scripts, including the structured error and process exit-status contract, see Scripting the launcher.
Limit query output¶
Interactive query output is limited to 100 rows by default. Piped input and --command or --file
return the full result unless you set a limit.
Use --max-rows 0 for unlimited interactive output.
For SQL syntax, functions, and data types, see the Exasol SQL reference.
Use Exasol Admin¶
Exasol Admin is available for cloud deployments. The installation output and exasol info show its
URL. Its credentials are stored in secrets.json.
The browser can display a warning because Exasol Admin uses a self-signed certificate. Verify that you are connecting to your deployment before accepting the certificate warning.
Exasol Admin is not available for local deployments.