Unable to filter Results

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?

@Erin Stellato

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

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.

• @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 ...

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. ..