Skip to content

Move Database

PerformanceGuard uses Microsoft SQL Server databases. For the SQL Server versions that your PerformanceGuard version supports, see Software Requirements.

Follow the procedure in Back Up Database and then return to this topic.

Restore Database on New SQL Server Instance

Section titled “Restore Database on New SQL Server Instance”
  1. Stop all PerformanceGuard services.
  2. Open Microsoft SQL Server Management Studio and connect to the required database server as sa user (that is with system administrator rights).
  3. In Microsoft SQL Server Management Studio’s Object Explorer, locate the pguard database.
  4. Right-click pguard and select Tasks > Restore > Database.
  5. Microsoft SQL Server Management Studio will typically remember your backed-up version of the PerformanceGuard database. When that’s the case, select pguard in the From database menu. If you can’t select pguard this way, select From device and click the browse button next to the field. Then click the Add button and locate your pguard.bak backup file at the location that you noted down when you backed up the database. When ready, click OK twice to return to the Restore Database dialog.
  6. Select the Restore Database dialog’s Options page. For every database file in the list, change the path to the required new location.
    The Options page of the Restore Database dialog with the Restore As paths of the database files highlighted
  1. Microsoft SQL Server Management Studio is now ready to restore your database at the new location, and leave it ready to use by rolling back any uncommitted transactions. If you want to further adjust any restore and recovery options, do this while you work on the Options page.

    When ready, click Next.

    The database will now be restored, and you’ll be able to view the progress. When the restoration is finished, you’ll see a confirmation message.

  2. In Microsoft SQL Server Management Studio, right-click the pguard database and select Properties to verify that the restored database matches your expectations, especially with regards to file size limits.

    When satisfied, click OK.

  3. In Microsoft SQL Server Management Studio’s toolbar, click New Query.

  4. Enter the following in the new query window. Remember to replace ‘password’ with the actual required password for your database.

USE PGUARD
IF NOT EXISTS(SELECT * FROM master.dbo.syslogins where loginname = N'pguard')
BEGIN
CREATE LOGIN pguard WITH PASSWORD = 'password', DEFAULT_DATABASE = pguard
CREATE USER pguard FOR LOGIN pguard WITH DEFAULT_SCHEMA = pguard
ALTER ROLE db_owner ADD MEMBER pguard
END
ELSE
BEGIN
ALTER LOGIN pguard WITH DEFAULT_DATABASE = pguard
ALTER USER pguard WITH DEFAULT_SCHEMA = pguard
END
When ready, click the **Execute** button.

11. Start all PerformanceGuard services again.

When the database has been moved, you must change the configuration of the PerformanceGuard services so that it reflects the new location of the database.

Change the configuration in setting.ini:

  1. Open [PerformanceGuard installation folder]\settings.ini

    1. Change the following entries:

      1. BE_DB_HOST= “New SQL server”
      2. BE_JDBC_CONNECTSTRING=jdbc:sqlserver://“New SQL server”;databaseName=pguard;
  2. Save Settings file

Change the configuration in setting.ini:

  1. Open [PerformanceGuard installation folder]\settings.ini

    1. Change the following entries:

      1. FE_DB_HOST= “New SQL server”
      2. FE_JDBC_CONNECTSTRING=jdbc:sqlserver://“New SQL server”;databaseName=pguardfe;
  2. Save Settings file

After Saving Settings.ini with the new configuration. Start all services, and check logs for connections success