This article was updated to support v11.7.8 of Goliath Performance Monitor.

This migration document will cover the process of migrating from your current Goliath Database from one SQL Server to another SQL Server. It will also facilitate migrating from one drive to another. There are 3 areas that will be covered:

1. Preparing the Goliath Server for the database transition
2. Migrating the database to its new location
3. Connecting Goliath to the new SQL Server

Please note, when migrating database from one SQL Server version to another may be some some SQL limitations. From previous customer experience, SQL Server versions 2008R2 and older may not be able directly migrate to SQL Server versions 2014 and newer. If this is what you’ll be attempting to do  we highlighly recommend that you first migrate the database to SQL Server version 2012, increase the database’s compatibility mode to 2012, and then from the 2012 instance migrate to the newer version.

Prerequisites

• Have access to a SQL sysadmin account to perform the migration, or the DBO account that Goliath is specifically using. 

Prepare the Goliath Server

1. Log onto the server where Goliath Performance Monitor is installed
2. Open Windows Services
3. Stop and temporarily Disable the ‘MonitorIT Server Service’
   1. Make note of the account that is running the MonitorIT Server Service, this account has DBO rights to the database

Migrate the Database

1. Open SQL Server Management Studio and connect to the appropriate SQL Server and Instance that is currently running the database
2. Right click on the Goliath database, and go to ‘Properties’
3. A ‘Database Properties’ pane will appear, in the left-hand menu of the pane choose the ‘Options’ page
4. On the options page, use the ‘Compatibility level’ drop down menu to ensure that the highest level is selected. If it is not, please make the change. When finished click ‘OK’ to close the pane.
5. Right click on the Goliath database, and go to ‘Tasks’ and then click ‘Detach’
   1. The database name is configurable but common names are ‘MonitorIT’, ‘Goliath’ and ‘GoliathDB’
   2. 
6. A ‘Detach Database’ window will appear, check the boxes for ‘Drop Connections’ and ‘Update Statistics’
   1. 
7. Select ‘OK’ to start the detaching process.
   1. Please note, depending on the size of the database this could take 2-20 minutes
   2. While the database is detaching you can identify the progress at the bottom left hand corner of the database
   3. If any error messages occur preventing you for detaching the database, repeat #6 above without checking the boxes
   4. 
8. When the database is finished detaching, the ‘Detach Database’ window will disappear
9. Using Windows File Explorer, navigate to the location of the database.
10. Copy the file and paste it into its new location as appropriate
    1. Depending on the circumstances, this would be to a new drive or the new SQL Server
11. Open SQL Server Management Studio and connect to the new database server/location
12. Right click on Databases and choose ‘Attach..’
    1. 
13. The ‘Attach Databases’ window will appear, click the ‘Add’ button to locate the database file
    1. 
14. Use the tree to navigate to the database file and once selected click ‘OK’
    1. 
15. This will bring you back to the ‘Attach Databases’ window, in the ‘Database Details’ section at the bottom of the pane, if there is a log file displayed select the ‘Log’ file type and then click ‘Remove’. If there is not one, continue to the next step.
    1. 
16. Then select ‘OK’ to complete attaching the database. Once the database is successfully attached the window will disappear

Connect Goliath to the new SQL Server

NOTE: If the Goliath Server is located remotely from them SQL Server, check the security properties for the database. You will need a Windows User with DBO rights to the database in order to complete the configuration. That same account will also need to be a local admin on the Goliath Server.

1. Log into your Goliath Performance Monitor Server
2. Go to WIndows Administrator Tools and Launch "ODBC-32bit"
   1. You can also open the Run window and type ‘C:\Windows\SysWOW64\odbcad32’
3. Once open, go to the System DSN tab
   1. 
   2. Note: If you have an existing DSN for ‘BreakoutRPM’ name, select ‘configure’ and rename it to ‘BreakoutRPM.Old’
4. Next click ‘Add’ and scroll through the list to select the driver type. We suggest using the SQL Native Client over the SQL Server option if it is available.
   1. 
5. Name the connection with the information listed below, when finished click ‘Next’
   1. Define the Name as ‘BreakoutRPM’
   2. Define Description as ‘Primary GPM Database’
   3. For ‘Server’ use the dropdown menu to pick the appropriate server name and instance name if appropriate. If the dropdown menu is empty, manually type in the name
   4. 
6. Keep the default settings to use the Integrated Windows authentication to connect to the database and select ‘Next’
7. Check the box next to ‘Change the default database to’ and select the appropriate database from the dropdown menu. Click ‘Next’
   1. 
8. Keep the defaults for the additional options and click ‘Finish
9. Select the ‘Test Data Source’ button to validate the connection. Click ‘OK’ to close all windows
   1. If your SQL Server was local, but now it is is remote, to complete the configuration please follow the below steps"
      1. Open Windows Services
      2. Find the ‘MonitorIT Server Service’ in the list, right mouse click, and choose ‘Properties’
      3. Go to the ‘Log on’ tab
      4. Specify the Windows account that has DBO rights to the MonitorIT database you attached on the SQL Server.
      5. Click ‘Apply’ and then ‘OK’ to close the window
      6. Select ‘Start Service’ and then ‘Restart the Service’.
      7. Once the service restart is complete, wait about 3-10 minutes before launching the product.
   2. If your SQL Server went from one remote server to another, go to Windows Services and restart the MonitorIT Server Service and then once it is finished, wait about 3-10 minutes before opening the product.