Azure Data Studio troubleshooting
Azure Data Studio tracks issues and feature requests using on a GitHub repository issue tracker for the
Report an issue you've experienced
Write good bug reports and feature requests
File a single issue per problem and feature request.
- Don't enumerate multiple bugs or feature requests in the same issue.
- Don't add your issue as a comment to an existing issue unless it's for the identical input. Many issues look similar, but have different causes.
The more information you can provide, the more likely someone will be successful reproducing the issue and finding a fix.
Include the following information with each issue:
- Version of Azure Data Studio
- Reproducible steps (1... 2... 3...) and what you expected versus what you actually saw.
- Images, animations, or a link to a video. Images and animations illustrate repro-steps but don't replace them.
- A code snippet that demonstrates the issue or a link to a code repository we can easily pull down onto our machine to recreate the issue.
Because we need to copy and paste the code snippet, including a code snippet as a media file (that is,
.gif) isn't sufficient.
- Errors in the Dev Tools Console (Help > Toggle Developer Tools)
Remember to take the following steps:
- Search the issue repository to see if the same issue already exists.
- Simplify your code around the issue so we can better isolate the problem.
Don't feel bad if we can't reproduce the issue and ask for more information!
How to set the logging level
Azure Data Studio
From the Command Palette (Ctrl/Cmd + Shift + P), run the Developer: Set Log Level... command to select the log level for the current session. This value isn't persisted over multiple sessions. If you restart Azure Data Studio, it reverts back to the default
If you want to enable debug logging for startup then set the log level to
Debug and run the Developer: Reload Window command.
MSSQL (Built-in extension)
Mssql: Log Debug Info user setting is set to true, then debug log info is sent to the
MSSQL output channel.
Mssql: Tracing Level user setting is used to control the verbosity of the logging.
Azure Data Studio logs and location
From the Command Palette (Ctrl/Cmd + Shift + P), run the Developer: Open Logs Folder command to open the path to the logs. There are many different types of log files that write there. A few of the commonly used ones are:
renderer1.log): this file is the log file for the main process.
telemetry.log: When the log level is set to
Trace, this file contains the telemetry events sent by Azure Data Studio
exthost#/exthost.log: Log file for the extension host process (this is only the process itself, not the extensions running inside it)
exthost#/Microsoft.mssql: Logs for the mssql extension, which contains much of the core logic for MSSQL-related features
sqltools.logis the log for SQL Tools service
exthost#/output_logging_#######: these folders contain the messages displayed in the
Outputpanel in Azure Data Studio. Each file is named
#-<Channel Name>. For example, the
Notebooksoutput channel may output to a file named
If you're asked to provide logs, zip up the entire folder to ensure that the correct logs are included.
Recover editor files after a crash
If Azure Data Studio crashes unexpectedly, restarting Azure Data Studio should reopen any unsaved editor files as well. If they don't, there may have been an error trying to reopen them. In that case, follow these steps to navigate to the folder containing the backups where you can manually open them to recover their contents.
- From the Command Palette (Ctrl/Cmd + Shift + P), run the Developer: Open User Data Folder command.
- In the folder that opens, navigate to the
This contains folders with randomly generated names. Within these folders are files that contain the editor backups (which include some additional metadata along with their text contents).