From d66d9dc264654070f30694725292d3b8fa65e763 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?V=C3=ADctor?= <45356126+vcarazo@users.noreply.github.com>
Date: Wed, 2 Oct 2024 17:21:36 +0200
Subject: [PATCH] Update
 moving-the-report-server-databases-to-another-computer-ssrs-native-mode.md

The correct order is detach an attach
---
 ...ort-server-databases-to-another-computer-ssrs-native-mode.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/reporting-services/report-server/moving-the-report-server-databases-to-another-computer-ssrs-native-mode.md b/docs/reporting-services/report-server/moving-the-report-server-databases-to-another-computer-ssrs-native-mode.md
index c380532b24f..7b2c86aa2d6 100644
--- a/docs/reporting-services/report-server/moving-the-report-server-databases-to-another-computer-ssrs-native-mode.md
+++ b/docs/reporting-services/report-server/moving-the-report-server-databases-to-another-computer-ssrs-native-mode.md
@@ -27,7 +27,7 @@ ms.custom:
   
 -   Temporary report and user session data that is stored in `reportservertempdb` are persisted when you move that database.  
   
- [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] provides several approaches for moving databases, including backup and restore, attach and detach, and copy. Not all approaches are appropriate for relocating an existing database to a new server instance. The approach that you should use to move the report server database varies depending on your system availability requirements. The easiest way to move the report server databases is to attach and detach them. However, this approach requires that you take the report server offline while you detach the database. Backup and restore actions are a better choice if you want to minimize service disruptions, but you must run [!INCLUDE[tsql](../../includes/tsql-md.md)] commands to perform the operations. Copying the database isn't recommended, specifically by using the Copy Database Wizard. It doesn't preserve permission settings in the database.  
+ [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] provides several approaches for moving databases, including backup and restore, attach and detach, and copy. Not all approaches are appropriate for relocating an existing database to a new server instance. The approach that you should use to move the report server database varies depending on your system availability requirements. The easiest way to move the report server databases is to detach and attach them. However, this approach requires that you take the report server offline while you detach the database. Backup and restore actions are a better choice if you want to minimize service disruptions, but you must run [!INCLUDE[tsql](../../includes/tsql-md.md)] commands to perform the operations. Copying the database isn't recommended, specifically by using the Copy Database Wizard. It doesn't preserve permission settings in the database.  
   
 > [!IMPORTANT]  
 >  The steps provided in this article are recommended when relocation of the report server database is the only change you are making to the existing installation. Migrating an entire [!INCLUDE[ssRSnoversion](../../includes/ssrsnoversion-md.md)] installation requires connection reconfiguration and an encryption key reset. For example, this configuration is required when moving the database and changing the identity of the Report Server Windows service that uses the database.