Merge pull request #311394 from rwestMSFT/patch-2

Remove Azure Data Studio

Author: prmerger-automator[bot]

articles/synapse-analytics/sql-data-warehouse/sql-data-warehouse-query-visual-studio.md

@@ -3,7 +3,7 @@ title: Connect to dedicated SQL pool (formerly SQL DW) with VSTS
 description: Query dedicated SQL pool (formerly SQL DW) in Azure Synapse Analytics with Visual Studio.
 author: ajagadish-24
 ms.author: ajagadish
-ms.date: 08/15/2019
+ms.date: 02/04/2026
 ms.service: azure-synapse-analytics
 ms.subservice: sql-dw
 ms.topic: conceptual
@@ -13,7 +13,6 @@ ms.custom: sfi-image-nochange
 # Connect to dedicated SQL pool (formerly SQL DW) in Azure Synapse Analytics with Visual Studio and SSDT
 
 > [!div class="op_single_selector"]
-> * [Azure Data Studio](../sql/get-started-azure-data-studio.md)
 > * [Power BI](/power-bi/connect-data/service-azure-sql-data-warehouse-with-direct-connect)
 > * [Visual Studio](sql-data-warehouse-query-visual-studio.md)
 > * [sqlcmd](../sql/get-started-connect-sqlcmd.md) 

articles/synapse-analytics/sql/connect-overview.md

@@ -6,7 +6,7 @@ ms.author: stefanazaric
 ms.service: azure-synapse-analytics
 ms.topic: overview 
 ms.subservice: sql
-ms.date: 09/23/2024
+ms.date: 02/04/2026
 ms.reviewer:  stefanazaric
 ms.custom:
   - devx-track-csharp
@@ -36,11 +36,11 @@ To find the fully qualified server name:
 
 ## Supported tools
 
-Use [Azure Data Studio](/azure-data-studio/download-azure-data-studio) or [SQL Server Management Studio (SSMS)](https://aka.ms/ssms).
+Use [SQL Server Management Studio (SSMS)](https://aka.ms/ssms) or the [MSSQL extension for Visual Studio Code](/sql/tools/visual-studio-code-extensions/mssql/mssql-extension-visual-studio-code).
 
-For serverless SQL pools:
-- [Azure Data Studio](/azure-data-studio/download-azure-data-studio) is fully supported starting from version 1.18.0. 
-- [SQL Server Management Studio](https://aka.ms/ssms) is partially supported starting from version 18.5, you can use it to connect and query only.
+For serverless SQL pools, the following tools are partially supported (connect and query only):
+- [Visual Studio Code](/sql/tools/visual-studio-code-extensions/mssql/mssql-extension-visual-studio-code)
+- [SQL Server Management Studio](https://aka.ms/ssms)
 
 ## Supported drivers and connection strings
 Synapse SQL supports [ADO.NET](/dotnet/framework/data/adonet/), [ODBC](/sql/connect/odbc/windows/microsoft-odbc-driver-for-sql-server-on-windows), [PHP](/sql/connect/php/overview-of-the-php-sql-driver?f=255&MSPPError=-2147217396), and [JDBC](/sql/connect/jdbc/microsoft-jdbc-driver-for-sql-server). To find the latest version and documentation, select one of the preceding drivers. To automatically generate the connection string for the driver that you're using from the Azure portal, select **Show database connection strings** from the preceding example. Following are also some examples of what a connection string looks like for each driver.
@@ -92,7 +92,7 @@ Synapse SQL standardizes some settings during connection and object creation. Th
 
 ## Recommendations
 
-For executing **serverless SQL pool** queries, recommended tools are [Azure Data Studio](get-started-azure-data-studio.md) and Azure Synapse Studio.
+For executing **serverless SQL pool** queries, the recommended tool Azure Synapse Studio.
 
 ## Related content
 

articles/synapse-analytics/sql/connection-strings.md

@@ -6,7 +6,7 @@ ms.author: stefanazaric
 ms.service: azure-synapse-analytics
 ms.topic: overview 
 ms.subservice: sql
-ms.date: 09/23/2024
+ms.date: 02/04/2026
 ms.reviewer:  stefanazaric
 ms.custom: devx-track-csharp
 ---
@@ -57,7 +57,7 @@ jdbc:sqlserver://yourserver.sql.azuresynapse.net:1433;database=yourdatabase;user
 
 ## Recommendations
 
-For executing **serverless SQL pool** queries, recommended tools are [Azure Data Studio](get-started-azure-data-studio.md) and Azure Synapse Studio.
+For executing **serverless SQL pool** queries, the recommended tool is Azure Synapse Studio.
 
 ## Related content
 

articles/synapse-analytics/sql/overview-features.md

@@ -7,7 +7,7 @@ ms.author: jovanpop
 ms.service: azure-synapse-analytics
 ms.topic: overview
 ms.subservice: sql
-ms.date: 03/24/2022
+ms.date: 02/04/2026
 ms.custom: sfi-ropc-nochange
 
 ---
@@ -124,11 +124,11 @@ You can use various tools to connect to Synapse SQL to query data.
 
 | Tool  | Dedicated | Serverless |
 | --- | --- | --- |
-| **Synapse Studio** | Yes, SQL scripts | Yes, SQL scripts can be used in Synapse Studio. Use SSMS or ADS instead of Synapse Studio if you are returning a large amount of data as a result. |
+| **Synapse Studio** | Yes, SQL scripts | Yes, SQL scripts can be used in Synapse Studio. Use SSMS or Visual Studio Code instead of Synapse Studio if you are returning a large amount of data as a result. |
 | **Power BI** | Yes | Yes, you can [use Power BI](tutorial-connect-power-bi-desktop.md) to create reports on serverless SQL pool. Import mode is recommended for reporting.|
 | **Azure Analysis Service** | Yes | Yes, you can load data in Azure Analysis Service using the serverless SQL pool. |
-| **Azure Data Studio (ADS)** | Yes | Yes, you can [use Azure Data Studio](get-started-azure-data-studio.md) (version 1.18.0 or higher) to query a serverless SQL pool. SQL scripts and SQL notebooks are supported. |
-| **SQL Server Management Studio (SSMS)** | Yes | Yes, you can [use SQL Server Management Studio](get-started-ssms.md) (version 18.5 or higher) to query a serverless SQL pool. SSMS shows only the objects that are available in the serverless SQL pools. |
+| **SQL Server Management Studio (SSMS)** | Yes | Yes, you can [use SQL Server Management Studio](get-started-ssms.md) to query a serverless SQL pool. SSMS shows only the objects that are available in the serverless SQL pools. |
+| **MSSQL extension for Visual Studio Code** | Yes | Yes, you can [use Visual Studio Code](/sql/tools/visual-studio-code-extensions/mssql/mssql-extension-visual-studio-code) to query a serverless SQL pool. SQL scripts and SQL notebooks are supported. Visual Studio Code shows only the objects that are available in the serverless SQL pools. |
 
 > [!NOTE]
 > You can use SSMS to connect to serverless SQL pool and query. It is partially supported starting from version 18.5, you can use it to connect and query only.

articles/synapse-analytics/sql/resources-self-help-sql-on-demand.md

@@ -7,7 +7,7 @@ ms.author: stefanazaric
 ms.topic: troubleshooting-known-issue
 ms.service: azure-synapse-analytics
 ms.subservice: sql
-ms.date: 09/26/2024
+ms.date: 02/04/2026
 ---
 
 # Troubleshoot serverless SQL pool in Azure Synapse Analytics
@@ -34,7 +34,7 @@ Usually, this problem occurs for one of two reasons:
 Your query might fail with the error message `Websocket connection was closed unexpectedly.` This message means that your browser connection to Synapse Studio was interrupted, for example, because of a network issue.
 
 - To resolve this issue, rerun your query. 
-- Try [Azure Data Studio](/azure-data-studio/download-azure-data-studio) or [SQL Server Management Studio](/sql/ssms/download-sql-server-management-studio-ssms) for the same queries instead of Synapse Studio for further investigation.
+- Try the [MSSQL extension for Visual Studio Code](/sql/tools/visual-studio-code-extensions/mssql/mssql-extension-visual-studio-code) or [SQL Server Management Studio](/ssms/sql-server-management-studio-ssms) for the same queries instead of Synapse Studio for further investigation.
 - If this message occurs often in your environment, get help from your network administrator. You can also check firewall settings, and check the [Troubleshooting guide](../troubleshoot/troubleshoot-synapse-studio.md).
 - If the issue continues, create a [support ticket](/azure/azure-portal/supportability/how-to-create-azure-support-request) through the Azure portal. 
 
@@ -187,7 +187,7 @@ The error `Query timeout expired` is returned if the query executed more than 30
 
 The error `Invalid object name 'table name'` indicates that you're using an object, such as a table or view, that doesn't exist in the serverless SQL pool database. Try these options:
 
-- List the tables or views and check if the object exists. Use SQL Server Management Studio or Azure Data Studio because Synapse Studio might show some tables that aren't available in serverless SQL pool.
+- List the tables or views and check if the object exists. Use SQL Server Management Studio or Visual Studio Code, because Synapse Studio might show some tables that aren't available in serverless SQL pool.
 - If you see the object, check that you're using some case-sensitive/binary database collation. Maybe the object name doesn't match the name that you used in the query. With a binary database collation, `Employee` and `employee` are two different objects.
 - If you don't see the object, maybe you're trying to query a table from a lake or Spark database. The table might not be available in the serverless SQL pool because:
 
@@ -1004,13 +1004,13 @@ Serverless SQL pool assigns the resources to the queries based on the size of th
 
 If you have queries with a query duration longer than 30 minutes, the query slowly returning results to the client are slow. Serverless SQL pool has a 30-minute limit for execution. Any more time is spent on result streaming. Try the following workarounds:
 
-- If you use [Synapse Studio](#query-is-slow-when-executed-by-using-synapse-studio), try to reproduce the issues with some other application like SQL Server Management Studio or Azure Data Studio.
-- If your query is slow when executed by using [SQL Server Management Studio, Azure Data Studio, Power BI, or some other application](#query-is-slow-when-executed-by-using-an-application), check networking issues and best practices.
+- If you use [Synapse Studio](#query-is-slow-when-executed-by-using-synapse-studio), try to reproduce the issues with some other application like SQL Server Management Studio or Visual Studio Code.
+- If your query is slow when executed by using [SQL Server Management Studio, Visual Studio Code, Power BI, or some other application](#query-is-slow-when-executed-by-using-an-application), check networking issues and best practices.
 - Put the query in the CETAS command and measure the query duration. The CETAS command stores the results to Azure Data Lake Storage and doesn't depend on the client connection. If the CETAS command finishes faster than the original query, check the network bandwidth between the client and serverless SQL pool.
 
 #### Query is slow when executed by using Synapse Studio
 
-If you use Synapse Studio, try using a desktop client such as SQL Server Management Studio or Azure Data Studio. Synapse Studio is a web client that connects to serverless SQL pool by using the HTTP protocol, which is generally slower than the native SQL connections used in SQL Server Management Studio or Azure Data Studio.
+If you use Synapse Studio, try using a desktop client such as SQL Server Management Studio or Visual Studio Code. Synapse Studio is a web client that connects to serverless SQL pool by using the HTTP protocol, which is generally slower than the native SQL connections used in SQL Server Management Studio or Visual Studio Code.
 
 #### Query is slow when executed by using an application
 

articles/synapse-analytics/sql/tutorial-connect-power-bi-desktop.md

@@ -6,7 +6,7 @@ author: azaricstefan
 ms.service: azure-synapse-analytics
 ms.topic: tutorial
 ms.subservice: sql
-ms.date: 05/20/2020
+ms.date: 02/04/2026
 ms.author: stefanazaric
 ms.custom: sfi-image-nochange
 
@@ -32,7 +32,7 @@ To complete this tutorial, you need the following prerequisites:
 
 Optional:
 
-- A SQL query tool, such as [Azure Data Studio](/azure-data-studio/download-azure-data-studio), or [SQL Server Management Studio (SSMS)](/sql/ssms/download-sql-server-management-studio-ssms).
+- A SQL query tool, such as the [MSSQL extension for Visual Studio Code](/sql/tools/visual-studio-code-extensions/mssql/mssql-extension-visual-studio-code), or [SQL Server Management Studio (SSMS)](/sql/ssms/download-sql-server-management-studio-ssms).
 
 Values for the following parameters: