Use this option if EPI was not used for the initial installation or previous upgrade.

1. Uninstall all current SQL Sentry monitoring services using Add/Remove Programs in Windows.

2. Close all SQL Sentry clients.

3. Download the Enhanced Platform Installer from the SolarWinds Customer Portal.

4. Double-click SolarWinds-SQLSentry-EPI-{Version}.exe. 

   Note:  The files are unpacked to C:\Program Files\SentryOne Framework.  

5. Run Command Prompt as Administrator and change directory to SentryOne Framework: 

   cd c:\Program Files\SentryOne Framework 

6. Add a new connection:

   Using Integrated Windows Authentication

   so addreg -n <connectionName> --connectionServer <serverName> --connectionDatabase <databaseName>

   Using SQL Server Authentication

   so addreg -n <connectionName> --connectionServer <serverName> --connectionDatabase <databaseName> --connectionUseIntegrated false --connectionUsername <SQLServerUserName> --connectionPassword <SQLServerUserPassword> --connectionPort <SQLServerConnectionPort>

7. Verify available connections are registered:

   so listreg

8. Push the upgrade package:

   so push -n <connectionName>

   Important:  If you are on a version older than 18.3, skip this step, and proceed straight to step 8 to continue.

9. Upgrade the SQL Sentry database to the latest version and push upgrade package:

   so upgradedb -n <connectionName>
   					

10. Install the SQL Sentry monitoring service (you will be prompted for the serviceAccount password):

    The --IAcceptLicenseTerms switch must be added to the command to acknowledge acceptance of the EULA:

    so install --IAcceptLicenseTerms -n <connectionName> -u <serviceAccount>

    Note:  The SQL Sentry monitoring service is now installed and running. 

    Important:  The EPI installation adds a SQL Sentry Client shortcut to the desktop, but does not install the client. Running the executable file that the shortcut points to opens the Client installer and then installs the Client on the machine. You can remove the SQL Sentry Client shortcut if you don't want to install the client. 

11. Launch the SQL Sentry client. You will see a loading dialog as files are downloaded from the SQL Sentry database for the latest version of the client. It may take a few minutes for the files to download. 

    Note:  To verify the status of the upgrade without launching the client, validate the package:

    so listpackage -n <connectionName>

    Note:  See the Install Additional Clients and Install Additional Monitoring Services sections of this article for instructions on installing the EPI compatible versions of the SQL Sentry client and monitoring service onto additional machines as needed.

Success: The SQL Sentry installation has been upgraded and is now ready for use. The next time you need to upgrade, use Option 1 for an Existing EPI Upgrade.

Option 3 allows you to upgrade from a pre v20 release to a v20+ release without having to uninstall/install the controller service on all machines with a monitoring service at the time of the upgrade. This is not the typical or recommended path. This options allows you to upgrade SQL Sentry controller services on your own schedule, if needed. It is not required to upgrade the controllers at the same time.

For this option, you'll need to upgrade the SQL Sentry framework on one machine. The instructions vary depending on which (if any) SQL Sentry components are installed on the machine where you are running the EPI upgrade. Read below to determine if you should use Option A or Option B.

Option A: Machine without services

On a machine that does not have the SQL Sentry monitoring or controller services, follow these steps:

1. If there's an existing installation of the SQL Sentry framework, open the Control Panel > Programs > Programs and Features. Select SQL Sentry, then select Uninstall to remove it before continuing.

2. Install the v20.0 SentryOne Framework. Double-click SolarWinds-SQLSentry-EPI-{Version}.exe. The files are unpacked to C:\Program Files\SentryOne Framework.

3. Run Command Prompt as Administrator and change the directory to SentryOne Framework:

   cd c:\Program Files\SentryOne Framework 

4. Verify that you have the correct connection to the SQL Sentry database:

   so listreg  

5. Push the .s1package to the SQL Sentry database:

   so push -n <connectionName> -f <packagePath>

   Note:  You can omit the -f option if you installed the SentryOne Frameworks installer with the version you want to upgrade to.

   Note:  If you do not enter a <packagePath>, then the default path and package will be used: C:\Program Files\SentryOne Framework\SolarWinds-SQLSentry-EPIUpgradePackage-{Version}.s1package

6. Validate available packages:  

   so listpackage -n <connectionName>

7. Start the upgrade. Note:  See more about using the upgrade command in the EPI Commands article.

   If your currently installed version is below 2020.8 use the following:

   so upgrade -n <connectionName> -t <packageVersion>

   If your currently installed version is 2020.8 or later, then the --IAcceptLicenseTerms is needed:

   so upgrade --IAcceptLicenseTerms -n <connectionName> -t <packageVersion>

8. Wait for the upgrade to complete before starting the SQL Sentry client.

   Note:  If you are using SQL Sentry Portal, see the upgrading section of the SQL Sentry Portal Configuration article to complete the upgrade steps for that service.

Option B: Machine with services

On a machine that has the SQL Sentry monitoring or controller services, follow these steps:

1. Run Command Prompt as Administrator and change the directory to SentryOne Framework:

   cd c:\Program Files\SentryOne Framework 

2. Verify that you have the correct connection to the SQL Sentry database:

   so listreg  

3. Uninstall the service:

   so uninstall -n <connectionName>

4. Uninstall the existing installation of the SentryOne framework by opening the Control Panel > Programs > Programs and Features. Select SQL Sentry, then select Uninstall to remove it before continuing.

5. Install the v20.0 SentryOne Framework. Double-click SolarWinds-SQLSentry-EPI-{Version}.exe. The files are unpacked to C:\Program Files\SentryOne Framework.

6. Install the SQL Sentry monitoring service (you'll be prompted for the password):

   Starting with version 2020.8, the --IAcceptLicenseTerms switch must be added to the command to acknowledge acceptance of the EULA:

   so install --IAcceptLicenseTerms -n <connectionName> -u <serviceAccount>

   Versions prior to 2020.8 use the following:

   so install -n <connectionName> -u <serviceAccount>

7. Push the .s1package to the SQL Sentry database:

   so push -n <connectionName> -f <packagePath>
   					

   Note:  You can omit the -f option if you installed the SentryOne Frameworks installer with the version you want to upgrade to.

   Note:  If you do not enter a <packagePath>, then the default path and package will be used: C:\Program Files\SentryOne Framework\SolarWinds-SQLSentry-EPIUpgradePackage-{Version}.s1package

8. Validate available packages:  

   so listpackage -n <connectionName>

9. Start the upgrade. Note:  See more about using the upgrade command in the EPI Commands article.

   If your currently installed version is below 2020.8 use the following:

   so upgrade -n <connectionName> -t <packageVersion>

   If your currently installed version is 2020.8 or later, then the --IAcceptLicenseTerms is needed:

   so upgrade --IAcceptLicenseTerms -n <connectionName> -t <packageVersion>

10. Wait for the upgrade to complete before starting the SQL Sentry client.

    Note:  If you are using SQL Sentry Portal, see the upgrading section of the SQL Sentry Portal Configuration article to complete the upgrade steps for that service.

The upgrade process involves uninstalling, then reinstalling SQL Sentry Portal. You must upgrade the SQL Sentry version first via EPI, before you can upgrade the SentryOne Portal version.

1. Open Command Prompt (use the Run as administrator option)

2. Change to the SentryOne Framework directory

   cd C:\Program Files\SentryOne Framework

3. Stop the SQL Sentry Portal service

   so stopmp -n <connectionName> -s <portalServerFQDN>

4. Uninstall the SQL Sentry Portal

   so uninstallmp -n <connectionName> -s <portalServerFQDN>

5. Install the SQL Sentry Portal

   Using Integrated Windows Authentication

   so installmp --IAcceptLicenseTerms -n <connectionName> -s <portalServerFQDN> -u <serviceAccount>

   Using SQL Server Authentication

   so installmp --IAcceptLicenseTerms --connectionUseIntegrated false --server <portalServerFQDN> --connectionServer <serverName> --connectionDatabase <databaseName> --connectionUsername <SQLServerUserName> --connectionPassword <SQLServerUserPassword>

   Versions prior to 2020.8 use the following:

   so installmp -n <connectionName> -s <portalServerFQDN> -u <serviceAccount> -b <ipAddress:port>

6. Start the SQL Sentry Portal service

   so startmp -n <connectionName> -s <portalServerFQDN>

   Note: 

   • The --server (-s) switch is for the server that will host SQL Sentry Portal (<portalServerFQDN>) and must be the Fully Qualified Domain Name (FQDN). If needed, this name can be found by using the list command to view the Controller Service value. See the EPI Commands article for additional information on using list.

     so list -t services -n <connectionName> 

   • The switch -b <ipAddress:port> is not valid in versions 2020.8.31 or later. This version uses the Portal Configuration Utility to make updates after installing.

     Prior to that release, it can be omitted if you're using the default value of 0.0.0.0:9991. Prior versions cannot use the Portal Configuration Utility with EPI and must set the binding during installation, or uninstall then reinstall to make changes.

   • See the Parameters & Examples section of the EPI article for more information on the <parameters> used such as <serverName> and <databaseName>. These are referring to the SentryOne database and the SQL Server that hosts it.

If this is for the first option, where EPI already exists, it's possible that SQL Sentry components were installed before using the EPI. For example, there may be clients connected to the SQL Sentry database that were installed pre-EPI. In this scenario, there are no bootstrappers running to manage those client processes, which means that the so upgrade command cannot control those pre-EPI clients. The pre-EPI clients will continue sending a heartbeat to the SentryOne, and the upgrade will be blocked until the clients are shut down.