r/SQL • u/No-Lettuce-1655 • May 22 '26
Oracle I built a SQL workspace inside VS Code — saved queries, version history, data compare, session monitor

I got tired of switching between VS Code and a separate DB tool every few minutes, so I built SQLLab — a VS Code extension that puts a full SQL workspace inside the editor.
What it does:
Connect to SQL Server, PostgreSQL, MySQL, Oracle, SQLite, DuckDB
Saved query library with full-text search (search name, description, and the SQL itself)
Every save creates a version — diff any two versions side by side
Data Compare: run two queries against different DBs and see SAME/DIFFERENT per row and column
Session Monitor: see blocked/active sessions, kill them from right-click
Batch Run: run multiple saved queries in parallel, track status per script
Parameterised SQL with Jinja-style {{ variable }} substitution
Schema-aware autocomplete (tables, columns, PKs, indexes)
Paginated results — no freezing on large datasets
Still early stage, so I’d really appreciate feedback:
What features are missing?
What would stop you from using it?
What DB workflow annoys you the most today?

13
u/sirchandwich May 22 '26
Vibecoded
-24
u/No-Lettuce-1655 May 23 '26
Every side project starts with vibes.
The real pain starts when Oracle, SQL Server, and large datasets enter the chat
11
9
8
1
u/lord_xl May 23 '26
The fact that the native Snowflake extension doesn't allow for saved queries is a big fail. I may look into your extension if it connects to Snowflake
-2
22
u/dbxp May 22 '26
You've been able to connect to DBs in VS code for years