Merge pull request #31757 from rwestMSFT/rw-0828-redirects-002

[BULK] Rewrite redirects (part 2)

Author: MikeRayMSFT

docs/relational-databases/administer-multiple-servers-using-central-management-servers.md

@@ -30,12 +30,12 @@ helpviewer_keywords:
 ## Create Central Management Server and server groups 
  To create a Central Management Server and server groups, use the **Registered Servers** window in [!INCLUDE[ssManStudioFull](../includes/ssmanstudiofull-md.md)]. Note that the Central Management Server should not be a member of a group that it maintains, to prevent accidental audit policy application that could interfere with the CMS itself. SSMS enforces this by preventing a server of the same name as the Central Management Server from being added to a group.
 
- Central Management Servers are [also available in Azure Data Studio](../azure-data-studio/extensions/sql-server-cms-extension.md).
+ Central Management Servers are [also available in Azure Data Studio](/azure-data-studio/extensions/sql-server-cms-extension).
 
  For how to create Central Management Servers and server groups, see [Create a Central Management Server and Server Group (SQL Server Management Studio)](../ssms/register-servers/create-a-central-management-server-and-server-group.md).  
 
 ## Next steps
 
 - [Administer Servers by Using Policy-Based Management](../relational-databases/policy-based-management/administer-servers-by-using-policy-based-management.md)  
 - [Create a Central Management Server and Server Group](../ssms/register-servers/create-a-central-management-server-and-server-group.md)
-- [SQL Server Central Management Servers extension for Azure Data Studio](../azure-data-studio/extensions/sql-server-cms-extension.md)
+- [SQL Server Central Management Servers extension for Azure Data Studio](/azure-data-studio/extensions/sql-server-cms-extension)

docs/relational-databases/backup-restore/back-up-a-transaction-log-sql-server.md

@@ -157,7 +157,7 @@ GO
 
 ## <a id="PowerShellProcedure"></a> Use PowerShell
 
-Set up and use the [SQL Server PowerShell Provider](../../powershell/sql-server-powershell-provider.md). Use the **Backup-SqlDatabase** cmdlet and specify **Log** for the value of the **-BackupAction** parameter.
+Set up and use the [SQL Server PowerShell Provider](/powershell/sql-server/sql-server-powershell-provider). Use the **Backup-SqlDatabase** cmdlet and specify **Log** for the value of the **-BackupAction** parameter.
 
 The following example creates a log backup of the `<myDatabase>` database to the default backup location of the server instance `Computer\Instance`.
 

docs/relational-databases/backup-restore/back-up-files-and-filegroups-sql-server.md

@@ -192,7 +192,7 @@ GO
 
 ## <a name="PowerShellProcedure"></a> Using PowerShell
 
-Set up and use the [SQL Server PowerShell Provider](../../powershell/sql-server-powershell-provider.md).
+Set up and use the [SQL Server PowerShell Provider](/powershell/sql-server/sql-server-powershell-provider).
 
 Use the **Backup-SqlDatabase** cmdlet and specify **Files** for the value of the **-BackupAction** parameter. Also, specify one of the following parameters:  
 

docs/relational-databases/backup-restore/back-up-multiple-databases-to-azure-blob-storage-powershell.md

@@ -34,7 +34,7 @@ The following are considerations for the sample scripts:
 
 - SQL Server PowerShell implements cmdlets to navigate the path structure that represents the hierarchy of objects supported by a PowerShell provider. When you have navigated to a node in the path, you can use other cmdlets to perform basic operations on the current object.
 
-  For more information, see [Navigate SQL Server PowerShell Paths](../../powershell/navigate-sql-server-powershell-paths.md).
+  For more information, see [Navigate SQL Server PowerShell Paths](/powershell/sql-server/navigate-sql-server-powershell-paths).
 
 - **Get-ChildItem** cmdlet: The information returned by the **Get-ChildItem** depends on the location in a SQL Server PowerShell path. For example, if the location is at the computer level, this cmdlet returns all the SQL Server database engine instances installed on the computer. Or, if the location is at the object level such as databases, then it returns a list of database objects. By default the **Get-ChildItem** cmdlet does not return system objects. Use the `–Force` parameter to see the system objects.
 

docs/relational-databases/backup-restore/copy-only-backups-sql-server.md

@@ -120,7 +120,7 @@ Backup-SqlDatabase -ServerInstance 'SalesServer' -Database 'Sales' -BackupFile '
 
 ### Set up and use the SQL Server PowerShell provider
 
-- [SQL Server PowerShell Provider](../../powershell/sql-server-powershell-provider.md)
+- [SQL Server PowerShell Provider](/powershell/sql-server/sql-server-powershell-provider)
 
 ## Related content
 

docs/relational-databases/backup-restore/create-a-full-database-backup-sql-server.md

@@ -363,7 +363,7 @@ Use the **Backup-SqlDatabase** cmdlet. To explicitly indicate a full database ba
 > [!NOTE]
 > These examples require the SqlServer module. To determine if it is installed, run `Get-Module -Name SqlServer`. To install, run `Install-Module -Name SqlServer` in an administrator session of PowerShell.
 >
-> For more information, see [SQL Server PowerShell Provider](../../powershell/sql-server-powershell-provider.md).
+> For more information, see [SQL Server PowerShell Provider](/powershell/sql-server/sql-server-powershell-provider).
 
 > [!IMPORTANT]
 > If you are opening a PowerShell window from within SQL Server Management Studio to connect to an installation of SQL Server, you can omit the credential portion as your credential in SSMS is automatically used to establish the connection between PowerShell and your SQL Server instance.

docs/relational-databases/data-tier-applications/data-tier-applications.md

@@ -75,7 +75,7 @@ The following tools support the DAC package and BAC package format:
 
 - [SqlPackage CLI](../../tools/sqlpackage/sqlpackage.md)
 - [SQL Server Management Studio](../../ssms/sql-server-management-studio-ssms.md)
-- [Azure Data Studio](../../azure-data-studio/what-is-azure-data-studio.md)
+- [Azure Data Studio](/azure-data-studio/what-is-azure-data-studio)
 
 In these tools, a database can be extracted to a *.dacpac* or exported to a *.bacpac*. Conversely, a *.bacpac* can be imported into a new database or a *.dacpac* can be published to a new or existing database.
 
@@ -84,8 +84,8 @@ In these tools, a database can be extracted to a *.dacpac* or exported to a *.ba
 The following tools support the DAC package format in addition to providing editing of SQL database projects:
 
 - [SQL Server Data Tools in Visual Studio](../../ssdt/sql-server-data-tools.md)
-- [Azure Data Studio](../../azure-data-studio/extensions/sql-database-project-extension.md)
-- [Visual Studio Code (VS Code)](../../azure-data-studio/extensions/sql-database-project-extension.md)
+- [Azure Data Studio](/azure-data-studio/extensions/sql-database-project-extension)
+- [Visual Studio Code (VS Code)](/azure-data-studio/extensions/sql-database-project-extension)
 
 In these tools, developers can design a database in an unconnected, client-side development environment. The tools can be used to create a DAC package, deploy a DAC package to a database, and import a database package into a SQL project.
 

docs/relational-databases/data-tier-applications/unpack-a-dac-package.md

@@ -59,7 +59,7 @@ Deploying the .dacpac to a test instance results in the contents of the .dacpac
 
 ### Deploy the .dacpac using Azure Data Studio
 
-1. Install the **SQL Server dacpac extension** in [Azure Data Studio](../../azure-data-studio/extensions/sql-server-dacpac-extension.md).
+1. Install the **SQL Server dacpac extension** in [Azure Data Studio](/azure-data-studio/extensions/sql-server-dacpac-extension).
 
 2. Connect to the desired instance. Right-click on the server node and select **Data-tier application wizard** from the menu.
 
@@ -116,5 +116,5 @@ namespace DacUnpack
 
 - [Data-tier Applications](../../relational-databases/data-tier-applications/data-tier-applications.md)
 - [SqlPackage Publish](../../tools/sqlpackage/sqlpackage-publish.md)
-- [SQL Server dacpac extension in Azure Data Studio](../../azure-data-studio/extensions/sql-server-dacpac-extension.md)
+- [SQL Server dacpac extension in Azure Data Studio](/azure-data-studio/extensions/sql-server-dacpac-extension)
 - [SQL Server Data Tools](../../ssdt/download-sql-server-data-tools-ssdt.md)

docs/relational-databases/data-tier-applications/upgrade-a-data-tier-application.md

@@ -285,4 +285,4 @@ $fileStream.Close()
 ## See also
 
 - [Data-tier Applications](../../relational-databases/data-tier-applications/data-tier-applications.md)
-- [SQL Server PowerShell](../../powershell/sql-server-powershell.md)
+- [SQL Server PowerShell](/powershell/sql-server/sql-server-powershell)

docs/relational-databases/data-tier-applications/validate-a-dac-package.md

@@ -49,9 +49,9 @@ There are two mechanisms for viewing the contents of a data-tier application (DA
 7.  Use the **Schema View** to review all of the objects in the schema, particularly reviewing the code in objects such as functions or stored procedures.  
 
 ### Publish the DAC package to a test instance
-Multiple tools are available to publish a DAC package to a test instance. The [SQL Server Dacpac extension](../../azure-data-studio/extensions/sql-server-dacpac-extension.md) for Azure Data Studio contains the **Data-tier Application Wizard**. We will walk through publishing a DAC package to a test instance.
+Multiple tools are available to publish a DAC package to a test instance. The [SQL Server Dacpac extension](/azure-data-studio/extensions/sql-server-dacpac-extension) for Azure Data Studio contains the **Data-tier Application Wizard**. We will walk through publishing a DAC package to a test instance.
 
-1. If needed, deploy a test instance using the [deployment wizard](../../azure-data-studio/deploy-sql-container.md).
+1. If needed, deploy a test instance using the [deployment wizard](/azure-data-studio/deploy-sql-container).
 
 2. Connect to your test instance in Azure Data Studio and right-click on the server node.  Select **Data-tier application wizard** from the context menu.
 
@@ -71,7 +71,7 @@ Under several scenarios you may want to view the difference between a database a
 
 ### All databases
 **View database changes by using schema compare**
-- Using the [Schema Compare extension in Azure Data Studio](../../azure-data-studio/extensions/schema-compare-extension.md#compare-schemas), the schema differences between an existing *.dacpac* and a database or two of the same can be viewed on Windows, macOS, and Linux.
+- Using the [Schema Compare extension in Azure Data Studio](/azure-data-studio/extensions/schema-compare-extension#compare-schemas), the schema differences between an existing *.dacpac* and a database or two of the same can be viewed on Windows, macOS, and Linux.
 
 - Using [SQL Server Data Tools in Visual Studio](../../ssdt/how-to-use-schema-compare-to-compare-different-database-definitions.md), the schema differences between an existing *.dacpac* and a database or two of the same can be viewed on Windows.
 
@@ -128,7 +128,7 @@ The SqlPackage CLI can be used with the [DriftReport action](../../tools/sqlpack
 ### All databases
 
 **View database changes by using SQL project publish**
-- Using the [SQL Database Projects extension in Azure Data Studio](../../azure-data-studio/extensions/sql-database-project-extension-build.md), the actions to be taken when a SQL project will be published to a database can be viewed on Windows, macOS, and Linux by selecting "Generate Script" during the publish process.
+- Using the [SQL Database Projects extension in Azure Data Studio](/azure-data-studio/extensions/sql-database-project-extension-build), the actions to be taken when a SQL project will be published to a database can be viewed on Windows, macOS, and Linux by selecting "Generate Script" during the publish process.
 
 - Using [SQL Server Data Tools in Visual Studio](../../ssdt/how-to-change-target-platform-and-publish-a-database-project.md#to-publish-a-database-project), the actions to be taken when a SQL project will be published to a database can be viewed on Windows as a deployment script.