Before you install or upgrade your SQL Server software, consider the following information:
- Uninstall Metasys software such as SCT and CCT before you upgrade the version of an existing SQL instance.
-
Microsoft SQL Server 2014, 2012, SQL Server 2008, and SQL Server 2008 R2 are no longer supported. For information about how to upgrade SQL Server, refer to SQL Server Software Installation and Upgrade Guide (LIT-12012240) .
- If your computer has SQL Server software installed, verify that the current version of SCT Release 15.0 supports this software. Go to Verifying your computer has a supported version of SQL Server software installed.
- A tool called the SQL Installer is provided on the License Portal with the Branch Tools download to help you install or upgrade to any supported version of SQL Server software. If you do not have this tool, refer to the SQL Server Software Installation and Upgrade Instructions (LIT-12012240) for details on how to install or upgrade SQL Server software. Also refer to SQL Server Software Installation and Upgrade Instructions (LIT-12012240) this document if you need to apply a new service pack (SP) to an existing installation of SQL Server software because the SQL Installer does not support service pack installations.
- To use the SQL Installer to install a full version of SQL Server software (for example, SQL Server 2017 Standard edition), you can download the install files for full Microsoft SQL Server. To use SQL Installer to install an Express version of SQL Server software (for example, SQL Server 2017 Express), download the SQL Server Express installation file from the Microsoft SQL Server Express website.
- The SQL Installer supports both unified ADS/ADX and split ADX installations , with or without the Metasys Advanced Reporting Services, as well as any SCT configuration. However, the SQL Installer does not support adding Reporting Services if you use SQL Server 2017 because these newer versions of SQL Server use a standalone Reporting Services installer. If you have a split ADX with the Metasys Advanced Reporting System, you install the Database Engine Services component of SQL Server on the database server and the Reporting Services component on the web/application server. If you have a split ADX without Metasys Advanced Reporting Services, you only need to install SQL Server on the database server.
-
The SQL Installer verifies that your computer has the prerequisites you need to install SQL Server. An error message appears if a prerequisite is not present. You need to install any missing software prerequisites before continuing.
- The SQL Installer provides an advanced mode that lets you edit the SQL Server command line options before you start the installation. You can also copy the options, paste them into a command window, and run the installation at a command prompt. However, use this method only if you are an advanced user who fully understands SQL Server software options.
- If you are installing SQL Server software manually, do not enable the C2 audit tracing feature. With C2 audit tracing enabled, SQL Server creates a large number of operational log files that might eventually fill the hard disk and cause the server to stop responding. However, if you install MVE, the MVE installer enables the C2 audit tracing feature for you. If you want to conserve hard disk space, be sure to disable C2 audit tracing after installing MVE.
- At Release 12.0.50, the Metasys Advanced Reporting System is compatible with SQL Server 2017, and SQL Server 2016 software, but is not compatible with SQL Server 2019.
- The SA password that you specify in the SQL Installer window must follow the rules for Microsoft complex passwords. For more information about complex passwords, refer to the Security Administrator System Technical Bulletin (LIT-1201528).
- As part of the installation, the SQL Installer may require you to select an instance name. If you are installing a unified ADS/ADX, a stand-alone SCT computer, or the database server of a split ADX, we recommend that you use the default instance name. If you are installing the web/application server of a split ADX, use the instance name of MSSQLSERVER. This requirement is because the ADX install and rename processes assume an instance name of MSSQLSERVER on the web/application server that runs the Reporting Services feature of SQL Server.
- SQL Server installation packages no longer include Management Tools after SQL Server 2016. If you use this server, or a later version, you must manually install the SQL Server Management Studio tool. For details on how to install SQL Server Management Studio after you install SQL Server software, refer to the SQL Server Software Installation and Upgrade Instructions (LIT-12012240).
-
If you are installing server software on a server class machine, ensure SQL Server software is installed and running before you install Metasys software. For a split ADX, the SQL Server software on the database server and SCT computer must be running.
- If after you upgrade to a newer version of SQL Server software, you need to open the archive database in an older version of SQL Server software, use the Export Database option in SCT. Then import the archive that uses an older version of SQL Server software into SCT.
If your computer has SQL Server software installed, go to Verifying your computer has a supported version of SQL Server software installed to verify that you have a version the software supports.
SQL Server configuration screen |
SQL Server Express edition selections |
SQL Server Standard or Enterprise edition selections |
---|---|---|
Setup role |
N/A |
SQL Server feature installation |
Feature selection |
Database engine services Management tools - Basic (if available) |
Unified ADX or SCT: Database Engine Services Reporting Services Management Tools - Basic Management Tools - Complete Database server on split ADX: Database Engine Services Management Tools - Basic Management Tools - Complete Web/application server on split ADX: Reporting Services Management Tools - Basic Management Tools - Complete |
Instance configuration |
Default Instance (Named instance is valid as well) |
Default Instance (Named instance is valid as well) Note: For a split ADX that will not be
renamed in the future, use the default instance for the SQL service on
the web/application server and a named instance for the SQL service on
the database server. Also, if two web/application servers point to one
database server, point each web/application server to a unique SQL Server
instance on the data server.
|
Server configuration |
SQL Server Database Engine: NT Service\SQLSERVERAGENT1 or NT AUTHORITY\SYSTEM2 SQL Server Browser: NT AUTHORITY\LOCAL SERVICE |
SQL Server Agent: NT Service\SQLSERVERAGENT1 or NT AUTHORITY\SYSTEM2 SQL Server Database Engine: NT Service\SQLSERVERAGENT1 or NT AUTHORITY\SYSTEM2 SQL Server Reporting Services: NT Service\SQLSERVERAGENT1 or NT AUTHORITY\SYSTEM2 SQL Server Browser: NT AUTHORITY\LOCAL SERVICE |
Database engine configuration |
Mixed Mode Specify SQL Server Administrators: BUILTIN\ADMINISTRATORS (Administrators) |
Mixed Mode Specify SQL Server Administrators: BUILTIN\ADMINISTRATORS (Administrators) |
Reporting services configuration |
N/A |
Unified ADX or SCT: Reporting Services Native Mode: Install and configure Web/application server on split ADX: Install but do not configure the report server. |
SQL Server configuration manager Protocols for <instance name> |
Named Pipes: Enabled TCP/IP: Enabled |
Named Pipes: Enabled TCP/IP: Enabled |