Create a read-only connection for exploration and label environments clearly before opening a production database. Inspect schemas and preview a limited result set before editing SQL or data. Keep credentials managed securely and verify transaction behavior, because the client does not remove the underlying database's permission or change-management requirements.
This is best suited to analysts and developers using multiple databases. Before committing a larger project, account for these trade-offs: supported features depend on drivers; enterprise-only capabilities are separate.
