[Feature Request]: Support for Parallel Query Execution in Separate Sessions

[hillsrobin]

Feature Description

• Allow each editor tab or file to maintain its own session context.-
• Enable true parallel query execution without manual connection duplication.
• Optionally, provide a setting to toggle session isolation behavior

Problem and Motivation

Currently, even when executing multiple .sql files or tabs, the extension throws the error:
"A query is already running for this editor session. Please cancel this query or wait for its completion."

This suggests that sessions are not truly isolated, even across different tabs or files. In Azure Data Studio, it was possible to run queries in parallel in separate windows or notebooks, which was extremely useful for managing multiple long-running tasks or monitoring different parts of a system simultaneously.

Use Cases

Running long-running queries while continuing to work in another session.
Monitoring multiple databases or environments concurrently.
Simulating concurrent workloads for testing or performance tuning.

Workaround

I’ve been able to work around this by creating separate connection profiles manually, but this is cumbersome and not intuitive for users expecting session isolation per tab or file.

Related Area

• Connection dialog
• Query results panel
• Query editor
• Object Explorer
• Table Designer
• Schema Compare
• Schema Designer
• Local container
• GitHub Copilot integration
• Query Plan Visualizer
• Other (please describe below)

If you selected "Other", please describe the area

No response

Confirmation

• I have searched existing feature requests and couldn't find a match
• I want to help implement this feature