SQL server requirements

SQL server requirements for all components

See the GCS Technology Matrix for SQL Server requirements for System Platform 2023 R2 SP1 components, including InTouch HMI 2023 R2 SP1.

Note: Match SQL Server version to operating system version.

We recommend that you install and configure the supported SQL Server version before you begin the System Platform installation program, especially if you expect Information Server to coexist, either on initial or subsequent installations, with the InTouch HMI, Application Server, or the Historian Server.

The System Platform installer will install all prerequisites except the SQL Server requirement for installing the Historian Server. If you select the Historian Server for installation, and if the supported version of SQL Server is not already installed, you must exit the installation program, install the supported SQL Server version, and then resume the installation.

Considerations for SQL server

• Alarm DB Logger To use the Alarm DB Logger, you must set the default SQL Server authentication mode from Windows-based to Mixed Mode.

• SQL Server Configuration Rights: While installing System Platform, configuration changes to SQL Server are required. If the installer does not have SQL Server administrative rights, the proper configuration of SQL Server may not be applied. A post-install aaConfig SQL utility enables you to verify if the SQL configuration has been performed.

• Maximum Server Memory: After installing SQL Server, Use SQL Server Management Studio to confirm that the Maximum Server Memory is configured to approximately 65% of the computer's total available RAM. By default SQL Server does not clamp this setting. The System Platform installation process will attempt to adjust it if it has the appropriate rights to configure SQL Server.

• Restoring a CAB: You cannot restore a Galaxy .cab file backed up in SQL Server 2012 or SQL Server 2008 to a node with an earlier version of SQL Server. For example, you cannot restore a Galaxy .cab file backed up in SQL Server 2012 to a node with SQL Server 2008. For example, you cannot restore a Galaxy .cab file backed up on SQL Server 2008 to a node with SQL Server 2005. SQL Server database backups from SQL Server 2005 forward are not backward-compatible. Attempting such a restore initializes, and the progress dialog box quickly displays 100% completion of restoring the database, but the Galaxy .cab restore operation does not actually complete, and no Galaxy Repository is created. When you start the IDE, the Galaxy is blank.

• Migrating SQL Server Versions: You can migrate a SQL Server database to a later version from any of two prior versions. For example, you can migrate to SQL Server 2012 from SQL Server versions 2008 or 2005. You can migrate to SQL Server 2008 from SQL Server versions 2005 or 2000. You cannot migrate directly from SQL Server 2000 to SQL Server 2012. Such a migration requires an intermediate version installation. For more information and helpful procedures, see the following Microsoft references:

  • Upgrade to SQL Server 2014

  • Migrate SQL Server 2000 to SQL Server 2012

  • Migrating to SQL Server 2008 R2

  • Migrating to SQL Server 2008

  • T-SQL scripts to migrate SQL server 2000 user databases to SQL server 2012

  • ALTER DATABASE Compatibility Level (Transact-SQL) SQL Server 2012

  • ALTER DATABASE Compatibility Level (Transact-SQL) SQL Server 2008 R2

• SQL Server Rights Requirements: SQL Server 2008 and later versions do not automatically create the BUILTIN\Administrators role delivered in SQL Server 2005. Because of this change to SQL Server, the Application Server 2014 installation process will create the necessary operating system user group (aaAdministrators) as well as the necessary SQL Server role. This automated process will provide the rights required to allow operations within the Galaxy Repository without the need for blanket BUILTIN\Administrator rights. The aaAdministrators group must be present and enabled. If you accidentally delete the aaAdministrators group from the Windows operating system, you can run either of two options to restore it:

  • Run the Change Network Utility from the Windows Start menu.

  • Run the aaConfig SQL Utility from the Windows Start menu.

If you accidentally delete the aaAdministrators group from the SQL Server security logins, you must run the aaConfig SQL Utility to restore it. Refer to the Application Server User's Guide, About ArchestrA User Accounts, for further information and procedures to restore the aaAdministrators group.

Considerations for SQL server express

• SQL Server Express is supported for use on a Galaxy Repository node and recommended for use only with small systems.

• If you plan to modify an InTouch HMI installation which has SQL Server Express installed, then add Application Server with full SQL Server, you must install the full SQL Server prior to modifying the InTouch HMI installation or installing Application Server.

• If you plan to use SQL Server Express with Information Server and System Platform on the same node, the following limitations apply:

  • Install Information Server first with the SQL Server Express default instance name set to "SQLEXPRESS". Then, install InTouch HMI. This scenario will work without issues because each component uses a dedicated instance of SQL Server Express.

  • If you install InTouch HMI first, the System Platform installer silently installs and configures SQL Server Express. Installing Information Server will fail during configuration with an error message stating: "SQL Server client components not found."

    To work around this issue, configure Information Server to use an instance of SQL Server Express (or a non-Express edition) on a remote node.

  • The computing capacity of SQL Server Express is limited to the lesser of one CPU socket or four processor cores.

• For InTouch HMI installations, the System Platform installer installs SQL Server Express, if these conditions are met:

  • No other SQL Server elements are installed on the computer at the time of installation.

  • You select only the InTouch Development and Runtime System Platform installation option. When you select InTouch Development and Runtime, a Galaxy Repository will be installed.

  • The installation program includes an option to not install SQL Server on an InTouch development computer. When the option is selected, it prevents SQL Server from being installed. Clear this option to automatically install SQL Server on a development computer.