How to Transition from Azure Data Studio to the MSSQL Extension for Visual Studio Code
Introduction
With Microsoft ending support for Azure Data Studio, developers who relied on this lightweight tool for SQL Server and Azure SQL query building need a new solution. Fortunately, Microsoft recommends switching to the MSSQL extension for Visual Studio Code—a modern, cross-platform alternative that integrates seamlessly into your existing development environment. This guide walks you through the process, from setting up VS Code to running your first query with the MSSQL extension. By the end, you'll have a custom, efficient workspace that handles everything from database exploration to integration with GitHub Copilot.

What You Need
- Visual Studio Code – The free, lightweight code editor (available for Windows, macOS, or Linux). If you do not already have it, download the latest version from the official site.
- An internet connection – To install the extension and connect to cloud databases like Azure SQL.
- SQL Server or Azure SQL credentials – Connection details (server name, authentication method, database name) for the databases you'll work with.
- Basic familiarity with VS Code – Knowing how to open extensions, use the command palette (Ctrl+Shift+P), and manage files will help you follow along smoothly.
Step-by-Step Guide
Step 1: Install Visual Studio Code
If you don’t have VS Code on your machine, head to code.visualstudio.com and download the installer for your operating system. Run the installer and follow the on-screen prompts. Once installed, launch VS Code to see the welcome page—this is your new home for SQL development.
Step 2: Install the MSSQL Extension
Open the Extensions view by clicking the square icon on the left sidebar or pressing Ctrl+Shift+X. In the search bar, type MSSQL. Look for the official extension by Microsoft (it should show a green SQL logo). Click Install. After installation, you may need to reload VS Code. The extension adds SQL language support, connection management, and query execution features.
Step 3: Connect to Your Database
Press Ctrl+Shift+P to open the command palette, then type MSSQL: Connect and select it. A new panel appears asking for your server details. Enter the name of your SQL Server or Azure SQL server, choose an authentication method (Windows, SQL login, or Azure Active Directory), and provide your credentials. Optionally, specify a database name. Once you connect, you’ll see your server listed in the SQL Server explorer pane on the left.
Step 4: Explore Databases and Write Queries
With the connection active, expand the server node in the explorer to see databases, tables, views, and other objects. Right-click any object to get a context menu for common actions like Select Top 1000 Rows or Script as Create. To write a new query, open a new SQL file (File > New File > SQL) or use the command palette’s MSSQL: New Query. Type your SQL statements—the extension provides syntax highlighting and IntelliSense for tables, columns, and keywords. Execute the query with Ctrl+Shift+E or by right-clicking and selecting Execute Query. Results appear in a tab below the editor.
Step 5: Use Advanced Features
The MSSQL extension includes many power features you may have used in Azure Data Studio. For example, you can run scripts from the command line using the integrated terminal, export query results to CSV or JSON, and manage database projects. Access these through the command palette by typing MSSQL: and browsing the list. You can also set up custom shortcuts for repetitive tasks.

Step 6: Integrate GitHub Copilot
One of the biggest advantages of moving to VS Code is the seamless integration with AI coding assistants. If you have a GitHub Copilot subscription, install the Copilot extension (GitHub Copilot and GitHub Copilot Chat). While writing SQL queries, Copilot can suggest completions, generate whole statements from natural language prompts, and even help debug performance issues. This combination turns your editor into a smart SQL development environment.
Step 7: Customize Your Workspace
VS Code lets you tailor the interface to your workflow. Install additional extensions for database management (e.g., SQL Server (mssql) for object scripting, Database Client for multiple connections) or productivity tools like Settings Sync. You can also change the color theme, enable SQL formatting extensions, and adjust keybindings. To save your setup for reuse, use File > Preferences > Profile to create a named profile.
Tips for a Smooth Transition
- Take advantage of migration guides – Microsoft provides documentation for moving from Azure Data Studio to the MSSQL extension. Check the official guide for detailed troubleshooting.
- Use the SQL Server explorer – It mirrors the database tree you were used to in Azure Data Studio, making object browsing intuitive.
- Set up multiple connections – You can connect to several servers simultaneously; each appears as a separate node in the explorer.
- Enable Auto Save – To avoid losing unsaved query files, go to File > Auto Save and choose a delay.
- Back up your Azure Data Studio settings – If you had custom snippets or keyboard shortcuts in ADS, export them and import into VS Code where possible.
- Experiment with the command palette – It’s the fastest way to find every MSSQL feature—memorize the Ctrl+Shift+P shortcut.
- Join the community – The VS Code SQL extensions have active GitHub repositories and forums where you can ask questions and stay updated on new releases.
Related Articles
- Azure Cosmos DB Conf 2026 Reveals AI-Driven Transformation: Flexible Schemas and Semantic Search Become Core for Global-Scale Apps
- How to Give Your AI Agent Secure AWS Access Using the MCP Server
- How to Prepare for AWS Service Discontinuations: A Step-by-Step Guide
- Mastering Top announcements of the What’s Next with AWS, 2026
- Aurora PostgreSQL Serverless: Launch a Production-Ready Database in Seconds with Express Configuration
- How to Design Scalable Cloud Storage Like Amazon S3: A 20-Year Legacy Guide
- AWS Weekly Update: Key AI Partnerships and Lambda Enhancements (April 27, 2026)
- 10 Key Insights on Scaling Microsoft's Sovereign Private Cloud with Azure Local