The workspace rail beside the object browser, with two connections open
Cmd+Option+0, or in Settings > General > Sidebar.
What each entry shows
One icon per workspace, top to bottom. The icon is the database engine’s symbol, tinted with the connection’s colour, so you can tell staging from production at a glance without hovering. The icon changes shape, not just colour, when a connection is not healthy: a warning triangle when it failed, and a disconnected symbol when it has no live session. Colour alone would be invisible to anyone who cannot distinguish red from grey. Under each icon is the database that workspace browses. Long names are shortened in the middle, so both ends stay recognisable. Hover an icon for the full connection name, host, and database. VoiceOver reads the same information plus the connection’s state. The workspace you are looking at is highlighted. Every window highlights its own, so the rail always tells you where you are. On servers that group objects by schema rather than by database, an entry stands for a schema. On a single-file or single-database engine, like SQLite, DuckDB, or BigQuery, a connection has one workspace and its entry is labelled with the connection’s name.When a workspace appears
Switching database adds an entry only when the one you are leaving has work in it. A workspace has work when it has a table open, a query you have typed, a file you opened, or edits you have not saved.
An entry goes away when its last tab closes and you are no longer browsing it. Nothing is closed for you, and the rail never removes a workspace you still have work in. The set is per session, so relaunching starts from the databases your restored tabs use.
Switching
Click an entry to go to it. Moving between two connections raises that connection’s window, returning you to the tab you last used there rather than an arbitrary one. Moving between two databases of one connection stays in the same window and moves what the sidebar lists. Each connection is its own window with its own set of tabs, and the tab bar along the top shows only that connection’s tabs. A new connection window opens over the one you were in, so switching reads as the window changing content until you move a window somewhere you want it. Open tabs are never closed or retargeted by a switch. A tab keeps the database it was opened against and keeps querying it, whichever workspace you are in. Clicking the workspace you are already in does nothing. The rail takes the keyboard too. Click into it and the arrow keys move the highlight, typing jumps to a name, and Return opens the workspace you land on.Closing
Right-click a workspace and choose Close Workspace to close every tab in it. A window holding a tab in another database stays open, because that tab is not part of the workspace you are closing. Unsaved work is confirmed first, the same as closing a window.Reordering
Drag entries to arrange them. The order is shared by every window and remembered across launches. Once you have arranged the rail, a workspace keeps its position when you close it, and returns to the same slot when you reopen it. Until then, workspaces are listed in the order their connections opened, and the databases of one connection are grouped together by name.Keys
Show Previous and Show Next Workspace move through the rail in the order it displays, not the order things were opened. Change any of these in Settings > Keyboard. If you had already assigned
Ctrl+Cmd+Up or Ctrl+Cmd+Down to something else, your assignment wins and the workspace command stays unbound until you free the chord again.
Related
- Tabs and Windows for how tabs and windows relate to connections
- Quick Switcher for searching within the current connection