Use the browser workbench
Browse tables, execute queries and keep useful scripts in your private workspace.
Open your database
Open a ready deployment, then choose Open browser workbench in Connection. Your DBTurbine session is checked on every request. No separate workbench password is needed. The editor uses your deployment’s customer database account, not a server administrator account.
Query and inspect
The workbench uses DbGate Community. Browse schemas and tables, open a SQL editor, execute statements and inspect results. Valkey uses its Redis-compatible key browser. Operations affect your live data: check your target and take a cloud backup before destructive changes.
Save a query
Use the editor’s Save command and give the script a useful name. Saved SQL and query history stay in a private workspace for this deployment. Unsaved editor tabs are kept only while the page is open; use Save before closing or reconnecting. These files are not database backups. Avoid saving passwords or sensitive result copies you do not need.
Reconnect after failover
A primary change can end existing query sessions. Use Reconnect in the workbench header to resolve the new writer. A session pauses after about fifteen minutes without requests; reopening starts it again and retains saved files. Create databases and database users through the main workspace so plan allowances apply.