[FEATURE] Add MSSQL-Connections #73
Description
Feature Summary
Add support for MSSQL connections in addition to the existing MySQL, PostgreSQL, and other database connections.
Problem/Use Case
Currently, only MySQL, PostgreSQL, and similar databases are supported. Many enterprise environments rely heavily on Microsoft SQL Server (MSSQL). Without native MSSQL support, users must rely on external tools or manual workflows, which leads to inefficiencies and context switching.
Proposed Solution
Provide first-class support for MSSQL connections. This should include:
- Secure authentication (SQL authentication, Windows/AD authentication if feasible).
- Connection string management.
- Query execution with syntax highlighting for T-SQL.
- Result export options (CSV, JSON, Excel).
- Integration with existing database workflows (e.g., saved queries, connection profiles).
Current Workaround
- Use external tools such as SQL Server Management Studio (SSMS), Azure Data Studio, or third-party clients.
- Manually export/import data between tools to bridge gaps.
- Maintain separate workflows, which reduces productivity.
Detailed Description
User Interface
- MSSQL should appear in the same "Add Connection" menu as MySQL and PostgreSQL.
- Users should be able to configure hostname, port, authentication type, and database.
- Connection test button for quick validation.
- Query editor with T-SQL awareness.
Integration Points
Would this feature need to integrate with:
- Shell/Terminal
- Database clients
- HTTP/API calls
- File system (for result export/import)
- External tools (specify): ___
- Other: ___
Alternatives Considered
- Continue using external tools (SSMS, Azure Data Studio).
- Use ODBC/JDBC bridge connections.
These alternatives are less efficient and lack native integration.
Additional Context
Related Issues/Discussions
None known at this time.
Implementation Notes
- Ensure compatibility with both on-premise SQL Server and Azure SQL Database.
- Support for encrypted connections (TLS).