Q&A

Elevate SQL Development with VS Code

• By David Ramel
• 09/22/2025

As SQL development increasingly becomes part of full-stack workflows, developers are looking for ways to simplify their tooling without compromising capability. While SQL Server Management Studio (SSMS) has long been the go-to environment for DBAs and database professionals, it often falls short of what modern developers need: speed, flexibility, and seamless integration with the tools they already use.

That's where Visual Studio Code--and specifically the MSSQL extension--comes in. Lightweight, cross-platform, and deeply extensible, VS Code is already a favorite among application developers. But with recent updates to the MSSQL extension, it's also becoming a compelling environment for SQL work. New features like GitHub Copilot integration, a visual Schema Designer, Schema Compare, and local SQL containers are reshaping how developers approach database design and query optimization--all from within the same editor they use to build their apps.

In his upcoming Live! 360 Orlando session, "Elevate SQL Development with VS Code," Microsoft Program Manager Carlos Robles will walk through the latest capabilities of the MSSQL extension and share practical tips for integrating SQL into modern dev workflows. Whether you're building cloud-native apps, managing cross-platform environments, or simply tired of switching tools to tweak a schema, this session promises a developer-centric look at how SQL development is evolving inside VS Code.

We caught up with Robles ahead of his talk to learn more about what inspired the session, how GitHub Copilot is transforming query tuning, and why VS Code might be the most underrated SQL tool you're not using yet.

VisualStudioMagazine:What inspired you to present a session on this topic?
Robles: I'm the PM for the MSSQL extension for VS Code--but I'm also a developer myself. I know how frustrating it can be to constantly switch between tools just to get basic things done--write code in one place, manage your schema in another. That disconnect slows developers down.

That's exactly why I'm excited about this session: to show how we're bringing all of that together in one place. Over the past eight months, we've added GitHub Copilot integration, Schema Compare, a visual Schema Designer, and local SQL containers--all focused on making SQL development faster, more intuitive, and better aligned with how developers work.

This session is a great chance to walk through those updates, show what's possible now, and--most importantly--connect with the community. I want to hear what's working for them, what's not, and what else they'd love to see next.

What advantages does VS Code offer over SQL Server Management Studio?
It's all about choosing the right tool for the job and meeting users where they are. SSMS is a great tool for DBAs and data professionals, but developers have different needs.

From a developer's perspective, VS Code just makes more sense. It's lightweight, cross-platform, and works smoothly whether you're coding locally, inside a dev container, building cloud-native apps, or working across multiple languages. The MSSQL extension brings the SQL experience right into that workflow--so there's no need to context-switch or fire up another tool just to run a query or make a quick schema change.

You also get things like GitHub Copilot, version control, extensions, and modern workflows all in one place. It's everything you need to work faster and stay focused--without leaving your editor.

How does the new Schema Designer change the way developers work with database objects?
The Schema Designer is a big win for productivity. It gives you a visual way to explore and edit your schema--so even if you're jumping into a legacy project or picking up someone else's work, you can quickly understand how everything connects. Whether you're using an ORM or writing raw SQL, it helps you move faster and onboard to projects with less friction.

How does Copilot complement your workflow when writing or optimizing queries?
GitHub Copilot is incredibly helpful, especially if you're not someone who lives and breathes query optimization. For many developers, tuning SQL has always felt like a bit of a black box. GitHub Copilot changes that.

It can look at your query, analyze the execution plan, and explain what's going on in plain language. But more importantly, it doesn't just describe the problem, it also suggests actual improvements. Whether it's missing indexes, bad joins, or inefficient patterns (like the classing N+1 issue), GitHub Copilot gives you practical ways to fix things without having to be a performance expert. It's like having someone on your team who understands SQL deeply and is always ready to help.

What kind of projects benefit most from switching to VS Code for SQL work?
Pretty much any project where SQL is part of the stack. If you're already using VS Code for building your app, whether it's in Node.js, Python, .NET, or anything else. Then it just makes sense to manage your database schema there too. It's especially useful in cloud-native, cross-platform, or containerized environments. You get to stay in the same tool and keep your workflow simple.

How can attendees learn more about this topic and prepare for your session?
I would recommend installing the MSSQL extension in VS Code and giving it a try. We've got plenty of YouTube videos and blog posts that walk through everything we've shipped so far. It's a great way to get a head start; and who knows, you might show up to the session with a few questions of your own.

Note: Those wishing to attend the session can save money by registering early, according to the event's pricing page. "Save $400 when you register by the Sept. 26 Super Early Bird deadline," said the organizer of the event, which is presented by the parent company of Visual Studio Magazine.