This article was updated to support v12.1.3 and newer 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, whether it be SQL Express to Full SQL or Full SQL to Full SQL. 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. Preparing & Migrating the database to its new location
3. Connecting Goliath to the new location

Please note, when migrating database from one SQL Server version to another there may be some limitations

Prerequisites

• Have SQL sysadmin access on the new SQL Server
• Have db_owner access to the database on the current SQL Server

Prepare the Goliath Server

1. Log onto the server where Goliath Performance Monitor is installed
2. Open Windows Services
3. Stop and 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 and will need to be given the rights again on the new SQL Server

Prepare & Migrate the Database

Prepare the Database

1. Open SQL Server Management Studio and connect to the SQL Server instance that is currently running the database
   1. This can be done locally or remote 
2. Right click on the Goliath database, and go to Properties
3. The Database Properties window will appear, in the left-hand menu of the window 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.
5. Next, in the left-hand menu of the window choose the Files page
   1. This page will list the Logical Name for the database files, as well as the Path to where the files reside. Please note the location as this information will be needed at a later step.
   2. The database is made up one mdf file, one ldf file, and then a good number of ndf files. All files normally start with the name of database.
   3. 
6. When finished click OK to close the window.
7. While still in SQL Server Management Studio, right click on the Goliath database, and in the menu that appears go to Tasks and then click Detach
   1. The database name is configurable but common names are GoliathDB, MonitorIT and Goliath.
   2. 
8. A Detach Database window will appear, check the boxes for Drop Connections and Update Statistics
   1. 1. 
9. Select OK to start the detaching process.
   1. 1. Please note, depending on the size of the database this can take some time
      2. While the database is detaching you can identify the progress at the bottom left hand corner of the detach database window
      3. If any error messages occur preventing you for detaching the database, repeat #2 above without checking the boxes
      4. 
10. When the database is finished detaching, the Detach Database window will disappear and if you refresh the Object Explorer pane the database will no longer be listed.
11. Using Windows File Explorer, navigate to the location of the database files.
12. Copy all of the database files and paste them into their new location as appropriate
    
    1. Depending on the circumstances, this would be to a new drive or onto the new SQL Server
       1. the mdf and ndf files will want to be put into the Data folder
       2. the ldf file will want to be put into the Log folder
    2. To determine the locations for the Data & Log folders on the new SQL Server you'll want to go to the Server Properties in SSMS and then Database Settings.
       1. Depending on the SQL Server's configuration, the folder locations could be the same or different.
13. In SQL Server Management Studio, connect to the new database server.
14. Right click the Databases folder and choose Attach.. from the list options
    1. 
15. The Attach Databases window will appear, click the Add button to locate the database file
    1. 1. 
16. Use the tree to navigate to the main database file (the mdf) and once selected click OK
    1. 1. 
17. This will bring you back to the Attach Databases window, in the Database Details section at the bottom of the pane you will see all of the files associated with the mdf (ie the ndf files and ldf file)
    1. 
18. Click OK to complete attaching the database. Once the database is successfully attached the window will disappear.
    1. 1. Depending on the size of the database, this process make take some time.
19. If this SQL Server that the database now resides on is remote from the Goliath Server, a Windows account must be assigned DBO right to the database. (Security>User>Properties>User Mappings>db_owner)
    1. 1. This account will also need to have local admin rights to the Goliath Server

Now that the database is attached to the new SQL Server location, please proceed to the next section.

Connect Goliath to the new SQL Server

NOTE: If the Goliath Server is located remotely from the SQL Server, check the security properties for the database. You will need a Windows User with db_owner 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-64bit
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 or remove it altogether.
4. Next click Add and scroll through the list to select the driver type. We suggest using the ODBC Driver 18 for SQL Server.
   
   1. This can be downloaded here if not already installed on the machine.
5. Name the connection with the information listed below, when finished click Next
   1. Define the Name as BreakoutRPM, case sensitive
   2. Define Description as Primary GPM Database
   3. For Server use the dropdown menu to pick the appropriate server instance name. If the dropdown menu is empty, manually type in the name.
      1. Please note, if the SQL Server utilizes a listening port other than 1433, the SQL Server should be formatted SQL_Server_name,ListeningPort.
         1. For example, SVR-SQL01,4454 or SVR-SQL01\PROD,4454.
         2. You can use this article for steps on how to check the port number.
   4. 
6. Keep the default settings to use the Integrated Windows authentication to connect to the database and select Next
7. Select Next again
8. Check the box to Trust Server Certificate and then click the Back button
   1. 
9. Check the box next to Change the default database to and select the appropriate database from the dropdown menu. Click Next
   1. 
10. Keep the defaults for the additional options and click Finish
11. 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. 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 db_owner rights to the Goliath 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-5 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.