Marco Conceptual

In this section, we will review the procedure for connecting to a Remote SQL Server Instance from the Installer. See below a link to download the Goliath Performance Monitor database file;

https://s3.amazonaws.com/goliathpm/Consulting/Database.zip

Prepare the Database Files

Prior to setting up the new server you will need to ensure that the original Goliath Performance Monitor SQL Database file is ready to be moved and the new SQL Server is up and running.

1. Stop the MonitorIT service

2. Detach the database and copy it from its current location, to the new SQL Server directory 3. Management Studio is available to connect to the new SQL Server to facilitate setting up the

database.

Stopping the MonitorIT Service

In this section you will learn how to stop the MonitorIT service. 1. Log into the server running SQL Express

2. Open Windows Services by going to ‘Control Panel > System and Security > Administrative

35

3. The ‘Services’ window will appear, locate and select ‘MonitorIT Server Service’ from the list

4. Click ‘Stop the service’ to the right

NOTE: A ‘Service Control’ window with a progress bar with appear displaying the progress of the service being

36

Backing up the old database

Now that the service is stopped we can bring the old SQL Express database to the new SQL Server 1. Open SQL Server Management Studio and Navigate to the ‘MonitorIT’ database

2. Right click the database, and go to ‘Tasks’ and then click ‘Backup’

3. A ‘Backup Database’ window will appear, click the ‘Add’ button at the bottom to choose the backup

37

4. A pop up will appear to choose the file name location, once finished select ‘OK’

5. Then selection ‘OK’ on the ‘Backup Database’ window and the database will begin to back up. Note: The backup process can take anywhere from 5 to 20 minutes to back up depending on the size of the

database.

Configure the new SQL Server

In this section we will cover the steps necessary to attach your Goliath Performance Monitor SQL Express Database to the new SQL Server Database.

Attach the new database

1. Open SQL Server Management Studio on the new SQL Server 2. Right click on Databases and choose ‘Restore Database..’

38

3. The ‘Restore Database’ window will appear, use the drop down menus to select the database

you backed up.

4. Once the database is selected click the ‘Verify Backup Media Button’

39

Connect Goliath Performance Monitor to your SQL Database

In this section we will cover the steps necessary to complete the final steps in the migration process by creating the necessary DSNs and appropriately modifying the windows service.

NOTE: If Goliath Performance Monitor will be located on a different server, check the security properties

for this database. There should be a Windows User with DBO rights to the database. This information will be needed for this section if applicable.

Create the Database DSNs

This section will cover the process for creating a connection to the database you have just attached to SQL. 1. Log into your Goliath Performance Monitor Server

2. Open the Run window and type ‘C:\Windows\SysWOW64\odbcad32’

3. Once open, go to the System DSN tab:

Note: If you have an existing DSN for ‘BreakoutRPM’ name, select ‘configure’ and rename it to

40

4. Next click ‘Add’ and scroll through the list to select the driver type: a. For local SQL Server instances: choose ‘SQL Server Native Client’

b. For remote SQL Server instances: choose ‘SQL Server’

5. Name the connection with the information listed below, when finished click ‘Next’

a. Define the Name as ‘BreakoutRPM’

b. Define Description as ‘Primary GPM Database’

c. For ‘Server’ use the dropdown menu to pick the appropriate server name

Note: For the SQL Server, be sure to pick the choice with the name in the correct format of the

41

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 ‘MonitorIT’ from the dropdown menu. Click ‘Next’

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 a. If your SQL Server is local, go to Windows Services and restart the MonitorIT Server Service

(Steps to do this are in Section III) and then once it is finished, restart MonitorIT server. b. If your SQL Server is remote go on to the next section for one last step

Configure the MonitorIT Windows Service for Remote SQL Databases

When connecting to a remote SQL Server, it is necessary to modify the MonitorIT Server Windows Service with the appropriate logon rights to access the database.

1. Open Windows Services by going to Run and typing ‘Services.msc’

2. Find the ‘MonitorIT Server Service’ in the list, right mouse click, and choose ‘Properties’

42

4. Specify a Windows account that has DBO rights to the MonitorIT database you attached on the SQL Server (we recommend using the ‘Browse’ function to ensure the account gets validated). 5. Click ‘Apply’ and then ‘OK’ to close the window

6. Select ‘Start Service’ and then ‘Restart the Service’. 7. Once that is done, restart the Monitor IT Server

43