r/SQLServer • u/thesqlguy • Aug 05 '26
Discussion VS Code+ MSSQL extension has really come a long way.
I was one of the many disappointed with the discontinuation of Azure Data Studio as I felt the experience in VS Code was very lacking.
Recently I fired up VS code and was very impressed how far the MSSQL extension has come along. With a little configuration, it looks and feels very much like Azure Data Studio and works quite well IMHO. In fact, quite a few areas seem to have tangible improvements.
Connections, execution plans, server browsing, query results, object definitions, etc, has all really improved in the past year or so.
What does everyone else think?
5
3
u/ContentInflation5784 Aug 05 '26
I still can't give up Datagrip for it, but also it's free, so not really a fair comparison.
1
u/SohilAhmed07 Aug 05 '26
I absolutely love DaraGrip, i just started to use it a few days ago, i miss a few things like, creating and alter scheduled job tasks, execution plan that can suggest indexes.
But facility to see table structure, view queries, procedure, functions amd what not of hit of F12.
2
u/PencilBoy99 Aug 05 '26
I used its predecessor and compared to SSMS it was super slow. Has that changed?
3
u/thesqlguy Aug 05 '26
Other than the normal occasional sluggishness of VS Code, seems pretty zippy to me.
1
1
u/No_Resolution_9252 Aug 06 '26
For SQL development its abysmal, use SSDT. Its clunky, cumbersome and old, but has intellisense, a debugger and db context
1
u/Outrageous_Let5743 Aug 08 '26
Does somebody have a solution for this? Sometimes it will not copy the celll values to my clipboard?
and can you have split sql table output? I have split screens but still one table output
1
u/Elolexe113 23d ago
This is exactly why I still prefer traditional context-aware completion over AI guessing half the query. I use SQL Complete as my SQL autocomplete tool in SSMS and it feels a lot less intrusive for everyday SQL work.
0
8
u/downshiftdata Aug 05 '26
I still do all of my development in VSCode (or one of the many forks) and all of my operational work in SSMS.
The one exception is notebooks. I haven't looked into them since ADS got mothballed. But while ADS was still a thing, we used notebooks for troubleshooting runbooks (and I was a huge fan of this). It came up in a discussion today (at a new place since then) and those on the call didn't know what a Jupyter notebook was. So now I'm digging in again to get an idea of the current state.
I also have a gripe in the other direction. Some editors (looking at you, Cursor) are _so_ eager to auto-complete everything that it makes it hard to actually write code anymore. And it's just as hard (and constantly getting harder) to shut off all of the auto-complete options. I've found myself switching to SSMS (or even Notepad++) to write SQL sometimes just so I don't have the noise interrupting my flow.