Merge pull request #35954 from rwestMSFT/rw-1124-ssms-url-007

prmerger-automator[bot] · web-flow · commit 41fed178e7c8 · 2025-11-27T18:09:02.000Z
[SCOPED] Update SSMS links (part 7)
diff --git a/azure-sql/database/analyze-prevent-deadlocks.md b/azure-sql/database/analyze-prevent-deadlocks.md
@@ -118,7 +118,7 @@ Learn more about each of these approaches in the [Prevent a deadlock from reoccu
 
 In this article, we use the `AdventureWorksLT` sample database to set up alerts for deadlocks, cause an example deadlock, analyze the deadlock graph for the example deadlock, and test changes to prevent the deadlock from reoccurring.
 
-We use the [SQL Server Management Studio](/ssms/install/install) (SSMS) client in this article, as it contains functionality to display deadlock graphs in an interactive visual mode. You can use other clients such as the [MSSQL extension for Visual Studio Code](/sql/tools/visual-studio-code-extensions/mssql/mssql-extension-visual-studio-code), [sqlcmd](/sql/tools/sqlcmd/sqlcmd-utility), or your favorite Transact-SQL querying tool to follow along with the examples, but you might only be able to view deadlock graphs as XML.
+We use the [SQL Server Management Studio (SSMS)](/ssms/sql-server-management-studio-ssms) client in this article, as it contains functionality to display deadlock graphs in an interactive visual mode. You can use other clients such as the [MSSQL extension for Visual Studio Code](/sql/tools/visual-studio-code-extensions/mssql/mssql-extension-visual-studio-code), [sqlcmd](/sql/tools/sqlcmd/sqlcmd-utility), or your favorite Transact-SQL querying tool to follow along with the examples, but you might only be able to view deadlock graphs as XML.
 
 ### Create the AdventureWorksLT database
 
diff --git a/azure-sql/database/connect-query-content-reference-guide.md b/azure-sql/database/connect-query-content-reference-guide.md
@@ -30,7 +30,7 @@ Watch this video in the [Azure SQL Database essentials series](/shows/azure-sql-
 
 | Quickstart | Description |
 | --- | --- |
-| [SQL Server Management Studio](connect-query-ssms.md) (SSMS) | This quickstart demonstrates how to use SSMS to connect to a database, and then use Transact-SQL statements to query, insert, update, and delete data in the database. |
+| [SQL Server Management Studio (SSMS)](connect-query-ssms.md) | This quickstart demonstrates how to use SSMS to connect to a database, and then use Transact-SQL statements to query, insert, update, and delete data in the database. |
 | [Azure portal](connect-query-portal.md) | This quickstart demonstrates how to use the [query editor](query-editor.md) to connect to a database (Azure SQL Database only), and then use Transact-SQL statements to query, insert, update, and delete data in the database. |
 | [Visual Studio Code](connect-query-vscode.md) | This quickstart demonstrates how to use Visual Studio Code to connect to a database, and then use Transact-SQL statements to query, insert, update, and delete data in the database. |
 | [.NET with Visual Studio](connect-query-dotnet-visual-studio.md) | This quickstart demonstrates how to use the .NET framework to create a C# program with Visual Studio to connect to a database and use Transact-SQL statements to query data. |
diff --git a/azure-sql/database/monitor-tune-overview.md b/azure-sql/database/monitor-tune-overview.md
@@ -16,7 +16,7 @@ monikerRange: "=azuresql||=azuresql-db||=azuresql-mi"
 # Monitor and performance tuning in Azure SQL Database and Azure SQL Managed Instance
 [!INCLUDE [appliesto-sqldb-sqlmi](../includes/appliesto-sqldb-sqlmi.md)]
 
-To monitor the performance of a database in Azure SQL Database and Azure SQL Managed Instance, start by monitoring the CPU and IO resources used by your workload relative to the level of database performance you chose in selecting a particular service tier and performance level. To accomplish this, Azure SQL Database and Azure SQL Managed Instance emit resource metrics that can be viewed in the Azure portal or by using [SQL Server Management Studio](/sql/ssms/sql-server-management-studio-ssms) (SSMS), based on [Microsoft Visual Studio](https://visualstudio.microsoft.com/downloads/).
+To monitor the performance of a database in Azure SQL Database and Azure SQL Managed Instance, start by monitoring the CPU and IO resources used by your workload relative to the level of database performance you chose in selecting a particular service tier and performance level. To accomplish this, Azure SQL Database and Azure SQL Managed Instance emit resource metrics that can be viewed in the Azure portal or by using [SQL Server Management Studio (SSMS)](/sql/ssms/sql-server-management-studio-ssms), based on [Microsoft Visual Studio](https://visualstudio.microsoft.com/downloads/).
 
 The following table presents a summary of monitoring capabilities in Azure SQL Database and Azure SQL Managed Studio.
 
diff --git a/azure-sql/managed-instance/point-to-site-p2s-configure.md b/azure-sql/managed-instance/point-to-site-p2s-configure.md
@@ -17,7 +17,7 @@ ms.custom:
 
 [!INCLUDE [appliesto-sqlmi](../includes/appliesto-sqlmi.md)]
 
-This quickstart teaches you how to connect to Azure SQL Managed Instance by using [SQL Server Management Studio](/sql/ssms/sql-server-management-studio-ssms) (SSMS) from an on-premises client computer over a point-to-site connection. For information about point-to-site connections, see [About Point-to-Site VPN](/azure/vpn-gateway/point-to-site-about).
+This quickstart teaches you how to connect to Azure SQL Managed Instance by using [SQL Server Management Studio (SSMS)](/sql/ssms/sql-server-management-studio-ssms) from an on-premises client computer over a point-to-site connection. For information about point-to-site connections, see [About Point-to-Site VPN](/azure/vpn-gateway/point-to-site-about).
 
 ## Considerations
 
diff --git a/azure-sql/managed-instance/winauth-azuread-run-trace-managed-instance.md b/azure-sql/managed-instance/winauth-azuread-run-trace-managed-instance.md
@@ -23,7 +23,7 @@ This article shares two options to run a trace against a managed instance: you c
 To use Windows Authentication to connect to and run a trace against a managed instance, you must first meet the following prerequisites:
 
 - [Set up Windows Authentication for Azure SQL Managed Instance using Microsoft Entra ID and Kerberos](winauth-azuread-setup.md).
-- Install [SQL Server Management Studio](/ssms/install/install) (SSMS) on the client that is connecting to the managed instance. The SSMS installation includes SQL Server Profiler and built-in components to create and run extended events traces.
+- Install [SQL Server Management Studio (SSMS)](/ssms/install/install) on the client that is connecting to the managed instance. The SSMS installation includes SQL Server Profiler and built-in components to create and run extended events traces.
 - Enable tooling on your client machine to connect to the managed instance. This may be done by any of the following:
     - [Configure an Azure VM to connect to Azure SQL Managed Instance](connect-vm-instance-configure.md).
     - [Configure a point-to-site connection to Azure SQL Managed Instance from on-premises](point-to-site-p2s-configure.md).
diff --git a/docs/includes/paragraph-content/sql-on-premises-vs-azure-similar-sys-views-include.md b/docs/includes/paragraph-content/sql-on-premises-vs-azure-similar-sys-views-include.md
@@ -12,7 +12,7 @@ Some Transact-SQL code examples written for SQL Server need small changes to run
 - `server_` - *prefix for SQL Server and Azure SQL Managed Instance*
 - `database_` - *prefix for Azure SQL Database, SQL database in Fabric, and SQL Managed Instance*
 
-Azure SQL Database and SQL database in Fabric support only database-scoped event sessions. [SQL Server Management Studio](/ssms/sql-server-management-studio-ssms) (SSMS) supports database-scoped event sessions for Azure SQL Database: an **Extended Events** node containing database-scoped sessions appears under each database in [Object Explorer](/ssms/object/object-explorer).
+Azure SQL Database and SQL database in Fabric support only database-scoped event sessions. [SQL Server Management Studio (SSMS)](/ssms/sql-server-management-studio-ssms) supports database-scoped event sessions for Azure SQL Database: an **Extended Events** node containing database-scoped sessions appears under each database in [Object Explorer](/ssms/object/object-explorer).
 
 Azure SQL Managed Instance supports both database-scoped sessions and server-scoped sessions. SSMS fully supports server-scoped sessions for SQL Managed Instance: an **Extended Events** node containing all server-scoped sessions appears under the **Management** folder for each managed instance in Object Explorer.
 
diff --git a/docs/relational-databases/backup-restore/restore-database-general-page.md b/docs/relational-databases/backup-restore/restore-database-general-page.md
@@ -15,7 +15,7 @@ f1_keywords:
 
 [!INCLUDE [SQL Server](../../includes/applies-to-version/sqlserver.md)]
 
-This article describes the various options found on the **General** page of the **Restore database** wizard in [!INCLUDE [ssManStudioFull](../../includes/ssmanstudiofull-md.md)]. The **General** page is used to specify information about the target and source databases for a database restore operation when you [restore a full database backup using SQL Server Management Studio](restore-a-database-backup-using-ssms.md) (SSMS). 
+This article describes the various options found on the **General** page of the **Restore database** wizard in [!INCLUDE [ssManStudioFull](../../includes/ssmanstudiofull-md.md)]. The **General** page is used to specify information about the target and source databases for a database restore operation when you [restore a full database backup using SQL Server Management Studio (SSMS)](restore-a-database-backup-using-ssms.md). 
 
 > [!NOTE]  
 > When you specify a restore task by using [!INCLUDE [ssManStudioFull](../../includes/ssmanstudiofull-md.md)], you can generate the corresponding [!INCLUDE [tsql](../../includes/tsql-md.md)] [RESTORE](../../t-sql/statements/restore-statements-transact-sql.md) script by selecting **Script** and then selecting a destination for the script.
diff --git a/docs/relational-databases/indexes/tune-nonclustered-missing-index-suggestions.md b/docs/relational-databases/indexes/tune-nonclustered-missing-index-suggestions.md
@@ -50,7 +50,7 @@ The missing indexes feature consists of two components:
 
 [Execution plan overview](../performance/execution-plans.md) can be generated or obtained in multiple ways:
 
-- When writing or tuning a query, you can use [SQL Server Management Studio](/ssms/menu-help/about-sql-server-management-studio) (SSMS) to [display the estimated execution plan](../performance/display-the-estimated-execution-plan.md) without running the query, or execute the query and [display an actual execution plan](../performance/display-an-actual-execution-plan.md).
+- When writing or tuning a query, you can use [SQL Server Management Studio (SSMS)](/ssms/sql-server-management-studio-ssms) to [display the estimated execution plan](../performance/display-the-estimated-execution-plan.md) without running the query, or execute the query and [display an actual execution plan](../performance/display-an-actual-execution-plan.md).
 - [Monitor performance by using the Query Store](../performance/monitoring-performance-by-using-the-query-store.md), when enabled, collects execution plans.
 - You can identify cached execution plans by querying DMVs such as [sys.dm_exec_text_query_plan](../system-dynamic-management-views/sys-dm-exec-text-query-plan-transact-sql.md).
 
diff --git a/docs/relational-databases/polybase/polybase-virtualize-parquet-file.md b/docs/relational-databases/polybase/polybase-virtualize-parquet-file.md
@@ -25,7 +25,7 @@ For more information on data virtualization, see [Introducing data virtualizatio
 To use the S3-compatible object storage integration features, you need the following tools and resources:
 
 * Install the PolyBase feature for SQL Server.
-* [Install SQL Server Management Studio](/ssms/install/install) (SSMS).
+* Install [SQL Server Management Studio (SSMS)](/ssms/install/install).
 * S3-compatible storage.
 * An S3 bucket created. Buckets cannot be created or configured from SQL Server.
 * A user (`Access Key ID`) and the secret (`Secret Key ID`) and that user is known to you. You will need both to authenticate against the S3 object storage endpoint.
diff --git a/docs/relational-databases/tables/delete-columns-from-a-table.md b/docs/relational-databases/tables/delete-columns-from-a-table.md
@@ -22,7 +22,7 @@ monikerRange: ">=aps-pdw-2016 || =azuresqldb-current || =azure-sqldw-latest || >
 
 [!INCLUDE [sqlserver2016-asdb-asdbmi-asa-pdw-fabricsqldb](../../includes/applies-to-version/sqlserver2016-asdb-asdbmi-asa-pdw-fabricsqldb.md)]
 
-This article describes how to delete table columns in [!INCLUDE [ssnoversion](../../includes/ssnoversion-md.md)] using [SQL Server Management Studio](/ssms/sql-server-management-studio-ssms) (SSMS) or [!INCLUDE [tsql](../../includes/tsql-md.md)].
+This article describes how to delete table columns in [!INCLUDE [ssnoversion](../../includes/ssnoversion-md.md)] using [SQL Server Management Studio (SSMS)](/ssms/sql-server-management-studio-ssms) or [!INCLUDE [tsql](../../includes/tsql-md.md)].
 
 > [!CAUTION]  
 > When you delete a column from a table, the column and all the data it contains are deleted.
