Restore the SQL Database to an Alternate Location on the Same Instance

This section provides information about restoring a FileStream enable SQL Database to an alternate location but on the same instance while renaming the database.

Follow these steps:

1. On the Restore screen, select the date for recovery from Recovery Point Date, the scheduled time for recovery from Time Range, and the RPS (SQL database) from the table, and then click Next.
2. 
2. On the Restore Options screen, under Destination, select Restore to alternative location, and then click Next.
3. Note: If the data you attempt to restore is encrypted, provide the password as needed.
4. 
3. On the Restore - Job level Options page, do the following, and then click Next:
4. Recovery State
• RECOVERY Mode: By default, this option is enabled. It makes the SQL database online to allow data recovery and provides you permission to access the restored database.
• NORECOVERY Mode: The database transitions to a ‘RESTORING’ state to prevent users from accessing the database. To restore the last backup and bring the database online for usage, use the RECOVERY Mode option.
5. Database Consistency Check
6. To make sure that the database is consistent after a restore, select the Run database consistency check after the restore check box. This option checks the physical and logical integrity of objects in an SQL Server database. The Mark the restore as failed if the consistency check fails option indicates when the restore job fails if the database consistency check fails for the selected database.
7. Miscellaneous
• Force restore over existing files or database: This option overwrites the existing database files located at the restore destination. Not selecting this option for an existing database file can make the restore incomplete. You can skip this option when the database file is new.
• Restricted user access after restore: This option restricts access to the database file for a specific group of users such as sysadmin, dbcreator, and/or db_owner. These users have permissions to modify the database.
• Note: If the source database was already in the restricted mode during the backup, the restored database automatically stays in the same mode.
8. 
9. The Restore Options- Alternate Location page appears.
4. Click the Destination Instance Name drop-down list to view the size and the FileStream enabled status of the selected database.
5. Note: If a database is FileStream Enabled, the Destination Instance Name field lists only FileStream Enabled servers. However, if the FileStream is not enabled, the Destination Instance Name displays both FileStream enabled and disabled databases.
5. To rename the database, type the New Database Name as needed.
6. 
7. Note: You can also perform restore to alternate location without renaming the database name using the Force restore over existing files or database option.
6. To configure or change the configuration at a database level, click the Configure button.
7. The Additional Database Options dialog appears.
7. In the Recovery Options tab, verify and make any changes to the database options, as needed.
8. In the Database Settings tab, do the following:
1. To select the Destination Location, click the Browse (…) button.
2. Note: When you change the destination location, it also updates the destination for all the database files.
2. Under File Name Settings (Optional), you can change the file names partially or fully. To replace the file name, provide the original file name in the Destination File Name Substring field and the new file name in the Replace With field.
3. Click Apply to make the changes.
4. Note: The new file names appear under the Destination File Name column.
9. 
9. Click OK to return to the Restore Options- Alternate Location page.
10. Click Next.
11. The Restore Summary page opens.
11. Verify if the settings are correct, and then click Finish to start the restore process.
12. 
13. After the restore finishes, view the restore status in the Activity Log along with the rename of the database.
14. 
15. The change in the database name reflects in the SQL Management Studio.
16.