[GH-ISSUE #2361] Simultaneous active queries to one server from one user session are not working #763

New issue

Open

opened 2026-03-07 20:54:21 +03:00 by kerem · 0 comments

kerem commented

2026-03-07 20:54:21 +03:00

Owner

Originally created by @Alkochm on GitHub (Feb 6, 2024).
Original GitHub issue: https://github.com/dbeaver/cloudbeaver/issues/2361

Two or more simultaneous active queries to one server from one user session are not working

Steps to reproduce the behavior:

Connect to MSSQL server
Open SQL Editor and start long running query (i.e. "WAITFOR DELAY '00:01:00'")
Open second SQL Editor and start short simple query (i.e. sp_who2)
Second SQLquery will wait untill first query finishes with "Loading..."

Simultaneous queries to diferent SQL servers do work in parallel.

Chrome Version 121.0.6167.140

I see that CB opens two connections per user to SQL (Main + Metadata) and it doesn't open additional connections to execute additional simultaneous queries. Also it doesn't seem to use Multiple Active Result Sets on main connection.

It is standard practice to run long query and look who is bloking you or who is blocked by you so I don't see why it should be by design.

Originally created by @Alkochm on GitHub (Feb 6, 2024). Original GitHub issue: https://github.com/dbeaver/cloudbeaver/issues/2361 Two or more simultaneous active queries to one server from one user session are not working Steps to reproduce the behavior: 1. Connect to MSSQL server 2. Open SQL Editor and start long running query (i.e. "WAITFOR DELAY '00:01:00'") 3. Open second SQL Editor and start short simple query (i.e. sp_who2) 4. Second SQLquery will wait untill first query finishes with "Loading..." ![image](https://github.com/dbeaver/cloudbeaver/assets/29176614/89161b1b-a9dc-40f3-9b98-1b5272feb1af) Simultaneous queries to diferent SQL servers do work in parallel. Chrome Version 121.0.6167.140 I see that CB opens two connections per user to SQL (Main + Metadata) and it doesn't open additional connections to execute additional simultaneous queries. Also it doesn't seem to use Multiple Active Result Sets on main connection. It is standard practice to run long query and look who is bloking you or who is blocked by you so I don't see why it should be by design.