SQLlyAzure Data Studio & VS Code
functionalConnections from settings.json, SQL notebooks as .ipynb, and snippet files: what comes over from Azure Data Studio and the VS Code MSSQL extension, and what goes back.
Microsoft retired Azure Data Studio in February 2026 and points its users at VS Code with the MSSQL extension. Both keep saved connections in the editor's settings.json, both save SQL notebooks as Jupyter .ipynb files, and both use the same snippet format. SQLly reads and writes all three, so whichever of the two you are leaving, your connections, notebooks and snippets come with you.
Connections
Azure Data Studio stores them under datasource.connections and datasource.connectionGroups; the VS Code MSSQL extension under mssql.connections. The file is:
| Azure Data Studio | VS Code | |
|---|---|---|
| macOS | ~/Library/Application Support/azuredatastudio/User/settings.json | ~/Library/Application Support/Code/User/settings.json |
| Windows | %APPDATA%\azuredatastudio\User\settings.json | %APPDATA%\Code\User\settings.json |
| Linux | ~/.config/azuredatastudio/User/settings.json | ~/.config/Code/User/settings.json |
Choose File → Import From Other Tools… and pick that file; SQLly reads both layouts, comments and trailing commas included. Server names written SQL Server style, as host,port or host\instance, are understood. Connection groups become projects, Windows authentication imports as integrated security, and SQL logins keep their user names. Azure Data Studio's PostgreSQL and MySQL extension connections import too. Saved passwords in the file are skipped on purpose.
To go the other way, choose File → Export for Other Tools → Azure Data Studio / VS Code (settings.json)…. The saved file holds a datasource.connections list for Azure Data Studio, with every connection you picked, and an mssql.connections list for VS Code's MSSQL extension, with only the SQL Server ones (PostgreSQL and MySQL connections have no place there, and the list is left out when there are none). Open your own settings with Preferences: Open User Settings (JSON) and copy those keys in, merging rather than replacing anything already there. If you already have a datasource.connectionGroups list, keep your existing ROOT group and add only the named groups from the file. Passwords are never written; the editor asks on first connect.
SQL notebooks
Open an Azure Data Studio or VS Code notebook (.ipynb) in SQLly as you would any notebook, and it saves back as .ipynb; Export Jupyter in the notebook toolbar writes one from any SQLly notebook. Code cells become SQL cells and text cells stay Markdown. The details, including what happens to stored outputs, are on Jupyter notebooks.
Snippets
Azure Data Studio's sql.json user snippets and VS Code .code-snippets files import through Preferences → Editor → Snippets & Quick Actions → Import from VS Code…. See VS Code snippets.