Connection-Probleme

[OSch24]

Type: Performance Issue

Hello everyone, first of all, I really enjoy working almost exclusively with ADS. I think the programme is great and would like to thank everyone who works with it.

I would just like to report a "problem" that occurs from time to time, but unfortunately I can't pinpoint why this happens.

This happens from time to time when I want to execute an SQL code or when I want to connect to an SQL server. Not always, but several times a day.

ADS really takes forever to connect to the server and execute a select top 10 * from table. This is not always ... I can sometimes work for hours and everything is great ... and then I want to start the sql again with F5 and it needs and needs and needs ... this sometimes takes up to 3 minutes ... then it suddenly works again.

If I switch to SQL Studio in the meantime, it works immediately. Sometimes I have SQL Studio open and ADS ... If it doesn't work with ADS again, I immediately test it on MSSMS and it always works there. I know it doesn't really help, but is there anything I can do?

mfg Oliver Schneider

Azure Data Studio version: azuredatastudio 1.47.1 (b6f7beb01f92adaa4b79b6b6f3ac704e95cafe6e, 2024-01-10T02:15:02.628Z) OS version: Windows_NT x64 10.0.19045 Restricted Mode: No Preview Features: Enabled Modes:

[github-actions[bot]]

We need more info to debug your particular issue. If you could attach your logs to the issue (ensure no private data is in them), it would help us fix the issue much faster.

1. First open the Settings page, find the Mssql: Tracing Level setting and change that to All then restart Azure Data Studio.
2. Open command palette (Click View -> Command Palette) and run the command Developer: Set Log Level... and set the level to Trace.
3. Run the repro scenarios.

4. Collect the following logs:

   Console Logs

   • Open Developer Tools (Help -> Toggle Developer Tools)
   • Click the Console tab
   • Click in the log area and select all text (CTRL+A)
   • Save this text into a file named console.log and attach it to this issue.
   • Developer Tools can be closed via Help -> Toggle Developer Tools

   Application Logs

   • Open command palette (Click View -> Command Palette)
   • Run the command: Developer: Open Logs Folder
   • This will open the log folder locally. Please zip up this folder and attach it to the issue.
5. Now you can revert the Log/Tracing levels changes made in step 1 and step 2.

[cheenamalhotra]

Hi @OSch24

Please gather and upload logs as per instructions and mask any server info from logs as needed.

[OSch24]

We need more info to debug your particular issue. If you could attach your logs to the issue (ensure no private data is in them), it would help us fix the issue much faster.

ok all clear. I'm just running all the logs once. But the console logs are also available in the Application Log folder.

I only have one problem, the log also contains our server names and path names, which I am not allowed to give out by the company.

Can I set somewhere that the path / server names are not logged? Or only anonymised?

[cheenamalhotra]

I don't think this is possible in automated way, there's only one file "mssql.log" we need, where you can find and replace server connection info and share the file.

[OSch24]

ok thank you very much, then I will do this.

[OSch24]

Hi, I looked again, there is no "mssql.log" in my system ... but a folder with "Microsoft.mssql" and there are 3 files there ...

The file "sqltools.log" looks interesting.

[OSch24]

Now I have such a "hanger" again ... I have the command

"SearchInAll 12" command. This is a procedure that shows me a few results.

Timestamp: 24-02-25 16:58:09.9926389

Now after 13 minutes I cancel the process ... Normally this select takes about 0.1 sec.

If I use another server with sp_who2 to display everything, I don't see that a "different" select is hanging or anything like that ... everything is completely normal.

Enclosed is a log file.

sqltools.log

[cheenamalhotra]

Looking closer into logs, I see query is executing find on time, but the call to ListDatabases maybe getting stuck and unresponsive leading to stuck results rendering..

24-02-25 16:58:09.9926389 pid:5880 tid:152 sqltools Verbose: 0 : eventTID:21632 SqlCommand.Set_CommandText | API | Object Id 14069, String Value = 'SearchInAll 12', Client Connection Id 5814284e-d955-4c36-9a05-f221750fc73e
...
24-02-25 16:58:09.9927501 pid:5880 tid:152 sqltools Verbose: 0 : eventTID:21632 SqlCommand.RunExecuteReaderTds | Info | Object Id 14069, Activity Id 6c04fb35-e46d-4447-bc54-a62d61b77953:1, Client Connection Id 5814284e-d955-4c36-9a05-f221750fc73e, Command executed as SQLBATCH, Command Text 'SearchInAll 12' 
...
24-02-25 16:58:10.0720886 pid:5880 tid:152 sqltools Information: 0 : Batch:'Batch Id:'0', Elapsed:'00:00:00.0794818', HasError:'False'' on Query:'untitled:SQLQuery_1' completed
24-02-25 16:58:10.0723337 pid:5880 tid:152 sqltools Verbose: 0 : Sending message of id[], of type[Event] and method[query/batchComplete]
24-02-25 16:58:10.0724623 pid:5880 tid:152 sqltools Information: 0 : Query:'untitled:SQLQuery_1' completed
24-02-25 16:58:10.0727633 pid:5880 tid:152 sqltools Verbose: 0 : Sending message of id[], of type[Event] and method[query/complete]
// Query and results processing completed here

// List Databases call received after 14 mins (when user cancels), till then there was no activity 🤔 
24-02-25 16:58:24.9766341 pid:5880 tid:12 sqltools Verbose: 0 : Received message with id[4458], of type[Request] and method[connection/listdatabases]

[OSch24]

Many thanks.

It's not always ... but sometimes it hangs and hangs and hangs ... What always helps is to switch to Mangement Studio or terminate ADS and reconnect.

Is there anything else I can do to fix the "problem"?

[MishraPriyanka1]

Hi,

I also face the same problem with Azure data Studio it gets stuck and then I have to close the Application and restart again then works fine. Any suggestions to fix the problem? Regards

[OSch24]

Hi,

Since the last update the problem has worsened. now i have the problem several times a day. when the problem occurs, ads just can't get a connection to the sql server anymore it works without end ... you just can't do anything. closing ads and restarting it helps a bit. It is hardly possible to work sensibly over the course of a day. I now have to fall back on SSMS more and more often.