Upgrading your SQL Server

Follow these steps to upgrade your primary SQL Server. Before doing so, ensure you have completed the required pre-upgrade steps. For more information, see Pre-installation.

This page contains the following information:

Note: This page also contains steps for upgrading a distributed SQL Server. You must upgrade your primary SQL Server before proceeding with these upgrades.

Primary SQL Server upgrade

The primary database, called the EDDS database, resides on the primary SQL Server. You must upgrade Secret Store before updating the primary database. For more information, see Upgrading the Secret Store.

Additionally, you must install or upgrade the Relativity service bus. You can then run the web and agent server installations in parallel.

Save the following files to the root directory of any server contributing to the Relativity environment:

  • Relativity.exe—the executable file that installs Relativity components determined by the values entered in the RelativityResponse.txt file.
      Notes:
    • You must save Relativity.exe on a drive local to the server. Running Relativity.exe from a shared location results in upgrade or installation failure.
    • The Relativity.exe file does not open a user interface. Use Install.bat to proceed with installation.
  • Install.bat—the code that prompts Relativity.exe to proceed with the installation process. You must edit line 11 of the Install.bat file with the exact name of the Relativity installation file.
     start /wait "" "INSERT EXACT NAME OF RELATIVITY INSTALLATION FILE" /log InstallLog.txt /responsefilepath=RelativityResponse.txt
      Notes:
    • You may need to run this file from an elevated command line prompt to avoid permission issues.
    • You must surround the name of the Relativity installation file with quotation marks.
  • RelativityResponse.txt—the text file that determines which components Relativity.exe installs, uninstalls, or upgrades on the server.
  • Note: Every line in the RelativityResponse.txt file that starts with ### is a comment and meant to provide instruction.

Open the RelativityResponse.txt file in a text editor and edit the parameters as follows to upgrade Relativity on the machine that serves the role of the primary SQL Server:

Common properties

Note: If you are upgrading to Relativity Server 2022, some values in your response file may now be stored in the Secret Store. These values are identified by the following message: "Value exported to Secret Store." You don't need to edit these values unless you want to update the Secret Store. For more information, see Secret Store.

  • INSTALLPRIMARYDATABASE - Set this value to one.
    INSTALLPRIMARYDATABASE=1
  • INSTALLDISTRIBUTEDDATABASE - Verify that this value is set to zero. You can't store the distributed database on the same machine as the primary database.
    INSTALLDISTRIBUTEDDATABASE=0
  • INSTALLDIR - Enter the installation directory. This is the target directory for all files related to the local installation. This path must be local to the machine and accessible by the server. You must use ASCII characters for this path.
    INSTALLDIR=C:\Program Files\kCura Corporation\Relativity
  • PRIMARYSQLINSTANCE - Enter the primary SQL instance. If you are installing to a cluster, specify the cluster and instance name. If you are installing to a named instance, specify the server and instance name. All features require this input.
    PRIMARYSQLINSTANCE=ML12
  • EDDSDBOPASSWORD - Enter the EDDSDBO password.
    EDDSDBOPASSWORD=MySecretPassword
  • SERVICEUSERNAME - Enter the service username. The Windows login must already exist.
    SERVICEUSERNAME=example\exampleusername
  • SERVICEPASSWORD - Enter the Service password.
    SERVICEPASSWORD=MySecretPassword
  • USEWINAUTH - Set the value to one to use Windows authentication for the SQL Server.
    USEWINAUTH=1

    Note: If the USEWINAUTH value is set to one, then the user running the installer must be a SQL sysadmin, and any values entered for SQLUSERNAME and SQLPASSWORD are ignored.

  • SQLUSERNAME - Enter the SQL username if you want to use SQL Server login authentication.
    SQLUSERNAME=mySqlUserName

    Note: This value is ignored if USEWINAUTH is set to one.

  • SQLPASSWORD - Enter the SQL password if you want to use SQL Server login authentication.
    SQLPASSWORD=myPassword

    Note: This value is ignored if USEWINAUTH is set to one.

Primary database properties

  • DEFAULTFILEREPOSITORY - Enter the default file repository. This path must be a shared folder to which both the user running the installer and the Relativity Service Account have read and write permissions.
    DEFAULTFILEREPOSITORY=\\yourmachine\FileShare
  • EDDSFILESHARE - Enter the EDDS fileshare path. This path must be a shared folder to which both the user running the installer and the Relativity Service Account have read and write permissions.
    EDDSFILESHARE=\\yourmachine\Fileshare
  • CACHELOCATION - A valid UNC path for the viewer cache location. The installer ignores this value during an upgrade. It only uses this value on a new installation of Relativity. This parameter is available in Relativity 9.5.292.12 and above. For more information, see Relativity installation.
    CACHELOCATION=\\yourmachine\ViewerCache
  • DTSEARCHINDEXPATH - Enter the dtSearch index. This path must be a shared folder to which both the user running the installer and the Relativity Service Account have read and write permissions.
    DTSEARCHINDEXPATH=\\yourmachine\dtSearch
  • RELATIVITYINSTANCENAME - Enter the Relativity instance name. Only set this value during a first-time installation. The installer ignores this value on upgrade.
    RELATIVITYINSTANCENAME=My Relativity Instance
  • ADMIN_EMAIL - Enter the email address that you want to use for the default Relativity admin account. If you don't specify an email address, the installer uses the default value of relativity.admin@relativity.com. This parameter is available for 9.5.342.116 and above.
    ADMIN_EMAIL=relativity.admin@relativity.com
  • SERVICEACCOUNT_EMAIL - Enter the email address that you want to use for the default Relativity service account. If you don't specify an email address, the installer uses the default value of serviceaccount@relativity.com. This parameter is available for 9.5.342.116 and above.
      Notes:
    • If you want to use a specific email address for the default Relativity admin or service account, you must enter it for each Relativity upgrade that you perform. If you entered a custom email address during a previous installation, it is overwritten by current email address that you entered or by the default email address when this parameter is blank.
    • Use different email addresses for the ADMIN_EMAIL and SERVICEACCOUNT_EMAIL parameters. If you use the same email address for both parameters, the installation fails.
    • The ADMIN_EMAIL parameter functions as the username for the default admin account. If you leave the ADMIN_EMAIL value blank, this username defaults to relativity.admin@relativity.com.
    SERVICEACCOUNT_EMAIL=serviceaccount@relativity.com
  • ADMIN_PASSWORD - Enter the password that you want to use for the default Relativity admin account. This parameter is available for 9.5.342.116 and above.
    ADMIN_PASSWORD=myPassword
  • SERVICEACCOUNT_PASSWORD - Enter the password that you want to use for the default Relativity service account. This parameter is available for 9.5.342.116 and above.
    SERVICEACCOUNT_PASSWORD=myPassword

    Note: To change the ADMIN_PASSWORD or SERVICEACCOUNT_PASSWORD password, you must also update the associated email address. If you enter a new password but do not update the email address, then new password is ignored. For example, if you use an existing or default email address, then the password remains unchanged. However, you can change the email addresses for the admin and service accounts without updating the password.

Common database properties

We recommend that the following database paths are local to the SQL Server and accessible. However, we also support UNC paths on SQL Server 2012 and above.

  • DATABASEBACKUPDIR - Enter the database backup directory.
    DATABASEBACKUPDIR=C:\Backup
  • LDFDIR - Enter the LDF directory.
    LDFDIR=C:\Logs
  • MDFDIR - Enter the MDF directory.
    MDFDIR=C:\Data
  • FULLTEXTDIR - Enter the full text directory.
    FULLTEXTDIR=C:\FullText

Save your edits to the RelativityResponse.txt file, and launch the Install.bat file to proceed with the upgrade.

A sample RelativityResponse.txt file for a primary SQL database upgrade using Windows authentication looks like this:

INSTALLPRIMARYDATABASE=1
INSTALLDIR=C:\Program Files\kCura Corporation\Relativity
PRIMARYSQLINSTANCE=ML12
EDDSDBOPASSWORD=MySecretPassword
SERVICEUSERNAME=example\exampleusername
SERVICEPASSWORD=MySecretPassword
DEFAULTFILEREPOSITORY=\\yourmachine\FileShare
EDDSFILESHARE=\\yourmachine\Fileshare
CACHELOCATION=\\yourmachine\ViewerCache
DTSEARCHINDEXPATH=\\yourmachine\dtSearch
RELATIVITYINSTANCENAME=My Relativity Instance
ADMIN_EMAIL=relativity.admin@relativity.com
SERVICEACCOUNT_EMAIL=serviceaccount@relativity.com
ADMIN_PASSWORD=myPassword
SERVICEACCOUNT_PASSWORD=myPassword
DATABASEBACKUPDIR=C:\Backup
LDFDIR=C:\Logs
MDFDIR=C:\Data
FULLTEXTDIR=C:\FullText
USEWINAUTH=1

Note: Every line in the RelativityResponse.txt file that starts with ### is a comment and meant to provide instruction.

Distributed SQL Server upgrade

If your Relativity environment uses a distributed SQL Server, then you need to run the installer on a machine other than the one that hosts the primary SQL database. After you have upgraded the primary SQL Server, you can upgrade the distributed database server and the web and agent server upgrades in parallel. Make sure that you review the steps for database server setup on Pre-installation page, including those in the Optionally configure an authentication token-signing certificate section.

Open the RelativityResponse.txt file in a text editor and edit the parameters as follows to upgrade Relativity on the machine that serves the role of the distributed SQL Server:

Common properties

  • INSTALLPRIMARYDATABASE - Set this value to zero. You can't store the distributed database on the same machine as the primary database.
    INSTALLPRIMARYDATABASE=0
  • INSTALLDISTRIBUTEDDATABASE - Set this value to one.
    INSTALLDISTRIBUTEDDATABASE=1
  • INSTALLDIR - Enter the installation directory. This is the target directory for all files related to the local installation. This path must be local to the machine and accessible by the server. You must use ASCII characters for this path.
    INSTALLDIR=C:\Program Files\kCura Corporation\Relativity
  • PRIMARYSQLINSTANCE - Enter the primary SQL instance. If you are installing to a cluster, specify the cluster and instance name. If you are installing to a named instance, specify the server and instance name. All features require this input.
    PRIMARYSQLINSTANCE=ML12
  • EDDSDBOPASSWORD - Enter the EDDSDBO password.
    EDDSDBOPASSWORD=MySecretPassword
  • SERVICEUSERNAME - Enter the service username. The Windows login must already exist.
    SERVICEUSERNAME=example\exampleusername
  • SERVICEPASSWORD - Enter the Service password.
    SERVICEPASSWORD=MySecretPassword
  • USEWINAUTH - Set this to one to use Windows authentication for the SQL Server.
    USEWINAUTH=1

    Note: If the USEWINAUTH value is set to one, then the user running the installer must be a SQL sysadmin, and any values entered for SQLUSERNAME and SQLPASSWORD are ignored.

  • SQLUSERNAME - Enter the SQL username to use SQL Server login authentication.
    SQLUSERNAME=mySqlUserName

    Note: This value is ignored if USEWINAUTH is set to one.

  • SQLPASSWORD - Enter the SQL password to use SQL Server login authentication.
    SQLPASSWORD=myPassword

    Note: This value is ignored if USEWINAUTH is set to one.

Distributed database properties

  • DISTRIBUTEDSQLINSTANCE - Enter the Distributed SQL instance. You can't store the distributed database on the same machine as the primary SQL Server.
    DISTRIBUTEDSQLINSTANCE=ML14

Common database properties

We recommend that the following database paths are local to the SQL Server and accessible. However, we also support UNC paths on SQL Server 2012 and above.

  • DATABASEBACKUPDIR - Enter the database backup directory.
    DATABASEBACKUPDIR=C:\Backup
  • LDFDIR - Enter the LDF directory.
    LDFDIR=C:\Logs
  • MDFDIR - Enter the MDF directory.
    MDFDIR=C:\Data
  • FULLTEXTDIR - Enter the full text directory.
    FULLTEXTDIR=C:\FullText

Save your edits to the RelativityResponse.txt file, and launch the Install.bat file to proceed with the upgrade.

A sample response file for a distributed SQL database upgrade using Windows authentication looks like this:

INSTALLDISTRIBUTEDDATABASE=1
INSTALLDIR=C:\Program Files\kCura Corporation\Relativity
PRIMARYSQLINSTANCE=ML12
EDDSDBOPASSWORD=MySecretPassword
SERVICEUSERNAME=example\exampleusername
SERVICEPASSWORD=MySecretPassword
DISTRIBUTEDSQLINSTANCE=ML14
DATABASEBACKUPDIR=C:\Backup
LDFDIR=C:\Logs
MDFDIR=C:\Data
FULLTEXTDIR=C:\FullText
USEWINAUTH=1

Note: Every line in the RelativityResponse.txt file that starts with ### is a comment and meant to provide instruction.

In-place SQL upgrade support

Relativity Customer support now supports in-place upgrade to SQL 2019. Please read the following stipulations to see if you can upgrade your current SQL Server Version to SQL Server 2019 or SQL 2017.

  • The base operating system of your SQL Server must be at a minimum of Windows Server 2016 to upgrade to SQL Server 2019. SQL Server 2017 is supported on Windows Server 2012 R2. Any Windows Server version other than what was previously listed will require an EDDS Migration to be performed to a Server with a proper Operating system Version and SQL Version. Relativity does not support in-place operating system upgrades. Contact Relativity Support for an updated EDDS migration guide.

  • If your SQL Server version is lower than SQL 2016, you will need to complete the EDDS migration because upgrading to SQL Server 2019 or SQL Server 2017 from versions lower than SQL Server 2016 has not been tested by Relativity. Contact Relativity Support for an updated EDDS migration guide.

  • Each environment is different. We recommend researching the settings that your specific environment may utilize before performing any upgrades.

  • Always make sure you have adequate and tested backups before performing any upgrades.

  • Although an in-place SQL upgrade is supported by Relativity, EDDS migration is the recommended way to perform a SQL Upgrade.