This article is in reference to Microsoft SQL Express which is commonly used during Proof Of Concepts (POCs). Upon installation of Goliath Performance Monitor, when trying to launch the technology the following error is displayed

How to tell if SQL Express Failed

1. When you launch the product for the first time and the webpage wont load. Sometimes a Database error pop-up will appear.
2. Open Windows Services and see if there is a service named “SQL Server (Goliath SQL)”, if there is not SQL Express failed to install

How to Resolve

1. Stop the MonitorIT Server Service
2. Open Windows File explorer and go to “C:\Program Files\MonitorIT\MSINSTALLS_X2019\SQL2019ExpressInstallFilesX64” and run “setup.exe”
   
   1.  
3. Once the SQL Install window opens, choose the first option for “New SQL Server…”
   1. 
4. Next through the installer changing the following settings
   1. On the “Instance Configuration” page, set the database name to “GoliathSQL”
      1. 
   2. On the “Database Engine Configuration” page add the “system” account to the SQL Server Administrators
      1. 
5. Complete the installer and Launch ODBC Data Sources (64-bit) from Windows Administrative Tools
6. When ODBC Data Sources (64-bit) launches, by default it will be on the User DSN tab. Switch to the System DSN tab
7. Click Add and scroll through the list to select ODBC Driver 18 for SQL Server then hit Finish
8. Complete the requested information as highlighted below and then choose 'Next'
   1. Name: BreakoutRPM
   2. Description: this can be anything you like
   3. Server: (local)\GoliathSQL
9. Keep all default settings on the How should SQL Server verify... page and click Next
   1. 
10. Check the box to enable Change the default database to: and set it to MonitorIT
    1. 
11. Check the box for “attach database as filename” and enter C:\Program Files\MonitorIT\Database\MonitorIT.mdf
12. Keep all default setting on the following page and click Finish
13. 
14. A SQL Server Setup window will appear. Click the Test Data Source... button to confirm the SQL Connection is successful. Then click OK to save the configuration.
    1. 
    2. 
15. If the test is not successful and you see a “CREATE FILE” error do the following:
    1. Save this configuration
    2. Copy the database file located at C:\Program Files\MonitorIT\Database\MonitorIT.mdf and paste it in C:\Program Files\Microsoft SQL Server\MSSQL14.GOLIATHSQL\MSSQL\DATA folder
    3. Reopen the ODBC entry you just created, and next through until you get to the page where the database name and path is configured
    4. Update the “attach file” path to be C:\Program Files\Microsoft SQL Server\MSSQL14.GOLIATHSQL\MSSQL\DATA\MonitorIT.mdf
    5. Test the database source again and it should be successful
16. Open Windows File Explorer and navigate to the \MonitorIT\Database folder
    1. Default location is C:\Program Files\MonitorIT\Database
17. Edit the file DatabaseVersioningTool.exe.config with the following settings and save once complete 
    1. On line 4, replace the data source=localhost setting with data source=____ where the blank is the SQL Server and instance name of where the database resides
       1. For example, if your database resides at SQL\Test12 then it should be data source=SQL\Test12
    2. On line 4, replace the initial catalog=MonitorIT1 setting with initial catalog=____ where the blank is the name of your database. 
       1. For example, if your database name is GoliathSB then it should be initial catalog=GoliathDB
    3. 
18. From Windows Files Explorer, within the \MonitorIT\Database folder go to File>Open Windows Powershell as administrator
    1. 
19. A Powershell console window will open, enter the command .\DatabaseVersioningTool.exe and click the enter key 
    1. For this step, be sure that the account you are running this as has SQL Server sysadmin rights
20. The Powershell console window will prompt you to Please Enter Go to Continue, type Go and hit the enter key to proceed
    1. 
21. The database will now be upgraded to match the current version of the product installed
    1. If you get any errors back, please reference the migration.log file in the Database folder.
       1. More often then not the error is due to permissions or network connection. Please resolve the issue and try steps 36-39 again. Feel free to open a support ticket for additional assistance if needed
22. Start the MonitorIT Server Service and wait about 2-3 mins