Docker and Databases
Database Explorer basics
Connect a database, browse schemas and tables, and handle connection failures clearly in ServerDesk.
Connecting a database
Create a saved database connection with the driver, host, port, database name, username, and password. Test the connection before saving so network or credential issues are caught immediately.
Using the Explorer
Once connected, browse schemas, tables, and result sets. This is useful for verifying that an application is pointing at the correct database and that expected data exists before you change code or config.
Connection failures
Database failures are surfaced as user-readable messages. Typical causes are wrong credentials, blocked ports, wrong database names, SSL mismatches, or a database service that is unavailable.
Need something else?
Move back into the searchable Help Centre, open the Support Hub, or use the public bug report and feature request routes if this article does not cover your workflow.