SQLlyFormats SQLly does not read yet
HeidiSQL, Beekeeper Studio, SSMS registered servers and a few others: why they are missing, and the quickest way across today.
Some tools keep connections in a format they do not document and do not offer as a stable export, so SQLly does not read or write it yet. Reverse-engineering a private file tends to work until the tool's next update, and a connection import that silently drops the TLS setting is worse than no import at all.
| Tool | Why not yet |
|---|---|
| HeidiSQL | Its settings export is a private line format with scrambled passwords; HeidiSQL does not describe it. |
| Beekeeper Studio | Connections live in the app's internal database, with no export. |
SSMS registered servers (.regsrvr) | A serialized object graph that Microsoft does not specify. |
| MySQL Workbench | connections.xml is an internal object dump without a published schema. |
| Sequel Ace, Postico, DbVisualizer | Private preference files, not documented as an interchange format. |
The quickest way across today
- Connection strings and URLs - most of these tools can copy a connection as a URL or connection string. In SQLly's connection editor click Paste URL:
postgres://,mysql://,sqlserver://, JDBC URLs, ADO.NET connection strings andredis://URLs all fill in the form. - Through a tool SQLly reads - if you already have DBeaver or DataGrip set up with the same servers, import from there.
- Write a SQLly connection file - for a team, a hand-written connection file provisions everyone at once.
If your tool publishes a connection format we have missed, tell me. A documented format usually makes it into the next release.