Restoring an Amicus database

---

 

Restoring a Database using SQL Management Studio

Abacus Data Systems\Gavel & Gown recommends that you have an IT person perform these steps.

1

Stop the Amicus Services (Amicus PE service, Amicus Daily Check Service and Amicus Exchange Service)

2

Open SQL Server Management Studio and login to the SQL Server you want to restore the database to.

It is best to either login as a Windows Administrator or as the SQL ‘sa’ user or Windows Authentication. Make sure the Server Name shows \\SERVER\Amicus (name of instance)

3

Expand Databases

4

Right click on the Amicus database and chose Tasks – Restore – Database

5

Click the ellipses button next to ‘From device’ under the ‘Restore’ section.

6

Set ‘File’ as the backup media and then click ‘Add’

7

Browse to the SQL backup (BAK) file you want to restore.

In the Restore Database dialog, type or select the name of the database you want this backup restored to.

If you select an existing database, it will be replaced with the data from the backup. If you type a database name which does not currently exist in your SQL Server installation, it will be created.

8

Next, select the restore point you want to use. Since a SQL backup file can hold multiple backups you may see more than one restore point listed. To database will be Amicus.

At this point, enough information has been entered for the database to be restored. However, SQL backup files store information about where data files are copied so if there are any file system problems such as a the destination directory not existing or conflicting data file names an error will occur. These problems are common when restoring a backup created on a different SQL Server installation.

To review and change the file system settings, click the Options page on the left in the Restore Database dialog.

On the options page, you will want to make sure the ‘Restore As’ column points to valid folder locations (you can change them as needed). The files do not have to exist, however the folder path must exist. If the respective files do exist, SQL Server follows a simple set of rules.

If the ‘To database’ (from the General page) matches the restore database backup (i.e. restoring to matching databases), the respective files will be overwritten as part of the restore.

If the ‘To database’ does not match the restore database backup (i.e. restoring to a different database), the ‘Overwrite the existing database with Replace’ will need to be checked for the restore process to complete.

Use this function with caution as you can potentially restore database backup information on top of data files from a completely different database.

Generally, you can tell the databases differ based on the ‘Original File Name’ which is the internal name SQL Server uses to reference the respective files.

Choose the top option – “Overwrite the existing database” and click Ok. You will see the message below when done.

If you receive an error “database in use” ensure that all the Amicus Services have been stopped. Exist SQL management Studio and restart the SQL Server and SQL Server Agent (Amicus) services.