Merge pull request #27908 from rwestMSFT/rw-0802-fix-relative-paths

prmerger-automator[bot] · web-flow · commit 409bf7a1bffd · 2023-08-02T21:53:10.000Z
[SCOPED] Fix relative paths
diff --git a/docs/relational-databases/replication/configure-replication-with-azure-ad-authentication.md b/docs/relational-databases/replication/configure-replication-with-azure-ad-authentication.md
@@ -30,7 +30,7 @@ To configure replication with Azure AD authentication, you must meet the followi
 
 - Have [Azure Arc-enabled](../../sql-server/azure-arc/connect.md) SQL Server 2022 starting with [Cumulative Update 6](/troubleshoot/sql/releases/sqlserver-2022/cumulativeupdate6). 
 - Configured Azure AD authentication for every server in the replication topology. Review [Tutorial: Set up Azure AD authentication for SQL Server](../../relational-databases/security/authentication-access/azure-ad-authentication-sql-server-setup-tutorial.md) to learn more. 
-- [SQL Server Management Studio (SSMS) v19.1 or higher](../../ssms/download-sql-server-management-studio-ssms.md) or [Azure Data Studio](/sql/azure-data-studio/download-azure-data-studio). 
+- [SQL Server Management Studio (SSMS) v19.1 or higher](../../ssms/download-sql-server-management-studio-ssms.md) or [Azure Data Studio](../../azure-data-studio/download-azure-data-studio.md). 
 - The user connecting to the publisher and subscriber is a member of the **sysadmin** fixed server role.
 - The connection must be encrypted using a certificate from a trusted Certificate Authority (CA) or a self-signed certificate.
    - If a self-signed certificate is used, it must be imported to the client machine and installed into the Trusted Certificates list for the client to trust the SQL Server. This requirement cannot be bypassed by selecting the **Trust server certificate** option in SQL Server Management Studio (SSMS) as it doesn't work with replication.
diff --git a/docs/relational-databases/track-changes/about-change-data-capture-sql-server.md b/docs/relational-databases/track-changes/about-change-data-capture-sql-server.md
@@ -284,7 +284,7 @@ Even if CDC isn't enabled and you've defined a custom schema or user named `cdc`
 
 Changing the size of columns of a CDC-enabled table using DDL statements can cause issues with the subsequent CDC capture process, resulting in **error 2628**. Remember that data in CDC change tables are retained based on user-configured settings. So, before making any changes to column size, you must assess whether the alteration is compatible with the existing data in CDC change tables.
 
-If the `sys.dm_cdc_errors` indicate that scans are failing due to the **error 2628** for change tables, you should first consume the change data in the affected change tables. After that, you need to [disable and then reenable CDC](/sql/relational-databases/track-changes/enable-and-disable-change-data-capture-sql-server) on the table to resolve the problem effectively.
+If the `sys.dm_cdc_errors` indicate that scans are failing due to the **error 2628** for change tables, you should first consume the change data in the affected change tables. After that, you need to [disable and then reenable CDC](enable-and-disable-change-data-capture-sql-server.md) on the table to resolve the problem effectively.
 
 ## Troubleshooting
 
diff --git a/docs/ssms/quickstarts/ssms-connect-query-sql-server.md b/docs/ssms/quickstarts/ssms-connect-query-sql-server.md
@@ -56,7 +56,7 @@ To connect to your SQL Server instance, follow these steps:
     |--------------|-----------------------|-----------------|
     | **Server type** | Database engine | For **Server type**, select **Database Engine** (usually the default option). |
     | **Server name** | The fully qualified server name | For **Server name**, enter the name of your SQL Server (you can also use *localhost* as the server name if you're connecting locally). If you're NOT using the default instance - ***MSSQLSERVER*** - you must enter in the server name and the instance name. </br> </br> If you're unsure how to determine your SQL Server instance name, see [Additional tips and tricks for using SSMS](../tutorials/ssms-tricks.md#find-sql-server-instance-name). |
-    | **Authentication** | Windows Authentication </br> </br> SQL Server Authentication </br> </br> Azure Active Directory Authentication | Windows Authentication is set as default. </br> </br> You can also use **SQL Server Authentication** to connect. However, if you select **SQL Server Authentication**, a username and password are required. </br> </br> **Azure AD Authentication** is available for SQL Server 2022 (16.x) and later versions. For step-by-step instructions on how to configure it, see [Set up Azure Active Directory authentication for SQL Server](/sql/relational-databases/security/authentication-access/azure-ad-authentication-sql-server-setup-tutorial) </br> </br> For more information about authentication types, see [Connect to the server (database engine)](../f1-help/connect-to-server-database-engine.md). |
+    | **Authentication** | Windows Authentication </br> </br> SQL Server Authentication </br> </br> Azure Active Directory Authentication | Windows Authentication is set as default. </br> </br> You can also use **SQL Server Authentication** to connect. However, if you select **SQL Server Authentication**, a username and password are required. </br> </br> **Azure AD Authentication** is available for SQL Server 2022 (16.x) and later versions. For step-by-step instructions on how to configure it, see [Set up Azure Active Directory authentication for SQL Server](../../relational-databases/security/authentication-access/azure-ad-authentication-sql-server-setup-tutorial.md) </br> </br> For more information about authentication types, see [Connect to the server (database engine)](../f1-help/connect-to-server-database-engine.md). |
     | **Login** | Server account user ID | The user ID from the server account used to log in to the server. A login is required when using **SQL Server Authentication**. |
     | **Password** | Server account password | The password from the server account used to log in the server. A password is required when using **SQL Server Authentication**. |
 
