Azure Data Studio
A cross-platform database tool for data professionals using on-premises and cloud data platforms on Windows, macOS, and Linux.
141 questions
Unable to filter Results
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(294.40000000000003, 94%, 38%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ES%3C/text%3E%3C/svg%3E)
Susja
751
Reputation points
Hello,
I hit the issue when I can't filter out Results.
In my case I have around 2,5 Millions records,
When I click on arrow to filter the record it failed and throws the error
I already increased Settings - Query Editor - Results ... Threshold till 9999999 but it didn't help. What else I could do?
Thanks
Azure Data Studio
{count} votes
-
Erin Stellato 721 Reputation points Microsoft Employee2023-08-25T19:12:50.1333333+00:00 Hi @Susja can you share the build of Azure Data Studio you are using (latest is 1.45.1), and to confirm, you are running a query against a SQL database, and the result set has more than 2.5 million rows. When you try to filter in the result set, you get this error, correct?
-
Susja 751 Reputation points
2023-08-26T17:22:13.7533333+00:00 I could confirm that I am using 1.45.1
I am running against SQL database
I ran query to get 1 million rows and got the same error.
Then I ran with 500000 rows - same issue
300000 - same issue
When I ran 100000 it worked as designed.
Thanks
-
Erin Stellato 721 Reputation points Microsoft Employee
2023-08-27T21:16:17.15+00:00 Hi @Susja - as noted in the notes for the Query Editor > Results: In Memory Data Processing Threshold setting, "increasing the value may impact performance". While you may have set the value extremely high, depending on the number of columns and their data type in your result, you may not have adequate memory available on your machine for the operation. Feel free to open an issue in the GitHub repo (https://github.com/microsoft/azuredatastudio/issues) and engineering can take a look - they will like request additional logs to provide more information about where the failure is occurring. You can also look at adding a filter or sort to your query, so that is handled before the data is brought client-side.
-
Susja 751 Reputation points
2023-08-28T19:50:11.3266667+00:00 - @Erin Stellato thanks for your thoughts.
- I tried query of 1 column of integer data type. It generated around 1 M rows.
- available memory ~ 3 Gb
I am not sure, but I doubt that's client machine issue ...
-
Susja 751 Reputation points
2024-01-24T23:02:37.9966667+00:00 Folks, I uploaded the last update. Now I run the following: Version: 1.47.1 (system setup) Commit: b6f7beb01f92adaa4b79b6b6f3ac704e95cafe6e Date: 2024-01-10T02:15:02.628Z VS Code: 1.82.0 Electron: 25.8.4 Chromium: 114.0.5735.289 Node.js: 18.15.0 V8: 11.4.183.29-electron.0 OS: Windows_NT x64 10.0.17763
Whatever I do ... 'Query Editor' filtering and sorting capabilities are restricted to 100000 records. If I run e.g. 200000 records ... it simply failed to open filter or sort. Note: I'm running on Windows 2019 with a plenty of resources ... It looks like bad memory handling because when I click of 'filter' it sorts very slow and throws this message ... eventually it failed to display dialog. ..
-
Susja 751 Reputation points
2025-04-02T22:40:23.8133333+00:00 Folks,
Today IT upgraded RAM on my Server. I had 8 Gb and now I have 16 Gb.
Unfortunately, nothing has changed in my case. I have exactly the same issue as before. I can filter Result Set grid with around 60 K records ... but when I have more than that ... it does not work. Sounds like the issue with Filter/number of records is nothing to do with RAM.
I'm completely stuck with it. I tried to ask folks from Git ... but no response ...Any other suggestions?
Here's my client:
Version: 1.51.1 (system setup)
Commit: 95e6a0e2142d267ff827c86b8e8155fa055a73df
Date: 2025-02-08T00:29:26.043Z
VS Code: 1.82.0
Electron: 30.5.1
Chromium: 124.0.6367.243
Node.js: 20.16.0
V8: 12.4.254.20-electron.0
OS: Windows_NT x64 10.0.17763
Thanks
Sign in to comment
Sign in to answer