Issue with multiple cursor projects open

[Avi-E-Koenig]

Title: dbhub-mssql-stdio does not allow multiple open cursor instances – only first retains access

Description:
When attempting to use multiple open cursors with dbhub-mssql-stdio, only the first cursor instance retains access to the database. Subsequent cursor instances fail to interact as expected, making it impossible to work with multiple concurrent cursors.

Steps to Reproduce:

1. Open a connection via dbhub-mssql-stdio.
2. Initialize a cursor and successfully execute queries.
3. Open a second cursor on the same connection.
4. Attempt to execute queries with the second cursor.

Expected Behavior:
Each open cursor instance should have independent access to the connection, allowing concurrent queries/operations without interference.

Actual Behavior:
Only the first cursor retains access. Subsequent cursors either fail silently or cannot execute queries.

Impact:
This limitation prevents applications from managing multiple concurrent queries via cursors, reducing usability in multi-query workflows.

Environment:

• dbhub-mssql-stdio version: latest
• OS: Windows 10 and 11
• SQL Server version: MSSQL

Additional Context:
If this is a design limitation, documentation should clarify cursor constraints. If unintended, it may require internal state handling fixes to allow multiple concurrent cursor access.

[tianzhou]

I haven't been able to reproduce the issue. Could you please paste the related code?

[tianzhou]

BTW, have you tried to run multiple dbhub instead sharding the same dbhub with multiple cursor instance?

[Avi-E-Koenig]

this seems to be stable thanks!