Grouping views

functional

See connections flat or grouped by client, project, environment, or server when a longer list needs a little order.

The explorer starts as a flat list. Use the header's overflow menu to switch the grouping view and arrange connections around the dimension that is useful right now.

Switching views

Click the ⋮ button at the top of the explorer (its tooltip reads Explorer options). The menu opens with a Group by section; the view you are in is checked. Pick another and the tree regroups immediately.

ViewGroups connections by
All (default)No grouping - every connection in one flat list.
By clientThe connection's client.
By projectThe connection's project.
By environmentThe connection's environment: Dev, Test, Staging, or Production. Local and unset land in “Unassigned”.
By serverThe connection's name, falling back to its host when the name is blank.

Your choice is saved with your connections, so the explorer comes back the same way the next time you launch SQLly. Regrouping only moves server rows into different folders: a server you had expanded keeps its open databases and folders, and nothing reconnects.

How the folders are built

  • Order. Group folders are sorted alphabetically, ignoring case, with “Unassigned” pinned last. Inside a folder, connections keep the order they have in the flat list.
  • Unassigned. A connection with no value for the chosen dimension, no client, no project, or a Local or unset environment, goes into “Unassigned” rather than disappearing.
  • Identity. In the client, project, and environment views, each folder header is tinted with that entity's color and shows its icon, so a client's group looks familiar wherever it appears. By server folders have no entity behind them, so they stay plain.
  • Server rows still carry their cues. Whatever the grouping, each saved server shows a small dot in its environment's color plus its connection-health dot, so the environment is visible even in the flat All view.
  • Folders are for viewing. A group header has no right-click menu; the actions live on the servers inside it.
SQLly
SQLly server explorer grouped by clientSQLly server explorer grouped by client
The explorer grouped by client, with colored group headers, and the overflow menu showing the grouping choices.
Spelling matters for folders. Folders are built from the text on each connection, so “Acme” and “acme” become two folders - even though both pick up the same client's color and safety policy, which match names case-insensitively. Choosing the name from the connection editor's suggestion list keeps them identical.

Example: thirty servers, four clients

Say you look after four customers, each with Dev, Staging, and Production databases on a mix of engines - thirty-odd connections in a flat list.

  1. Open each connection with Connection › Edit Connection... from its right-click menu, type its Client (the field suggests the names you already use), and pick its environment with the PROD / STAGE / TEST / DEV / LOCAL buttons.
  2. Choose Tools › Manage Clients, Projects & Environments... and give each client a color or a logo, and Production a red that is hard to miss.
  3. Switch to By client. Four tinted folders replace the long list; each holds that customer's connections, and the environment dot on every row tells Dev from Production at a glance.
  4. Before a release night, switch to By environment. Every production server, across all four customers, now sits in one folder.

Connections found through Azure discovery are listed below your saved connections and are not affected by the grouping view.