Windows SQL Server 2016
This document describes the minimum configuration requirements when installing the Software package application and data servers on a Microsoft® Windows - SQL Server 2016 server.
| Category | Configuration requirements |
|---|
| Operating system | - Microsoft Windows Server 2016.
- Microsoft Windows Server 2012 R2 x64 Essentials, Standard, and Datacenter.
|
| Computer | - Industry-standard server or virtual machine.
- Processors:
- Recommended: Intel® Xeon® E5 v3 or later, E7 v3 or later
- AMD OPTERON™ or EPYC™
- Avoid low energy processors, best performance with a clock speed above 2.4 GHz
|
| RAM | - 2 GB for the OS + 2 to 6 GB per database instance (average) + 60 MB per connected user.
|
| Disk space | - SQL server 2016: 6 GB minimum.
- For Sage X3 (reference folder and software): 4 GB.
- For the demo folder: 4 GB.
- For the exploitation folder: Depends on the data managed. A sizing tool is available to calculate the size requirements.
|
| Database software | Microsoft SQL Server 2016 x64 Standard or Enterprise Edition, installed with the following options:- A named instance is required. It will be used to create the product database.
- Regardless of the instance type, it must have the following characteristics:
- Sorting (collation) order should be Latin1_General_BIN
- Mixed mode is mandatory to support authentication both by Windows and by SQL Server.
- Access to the sa user.
- By default, communication by TCP/IP or Namepipe is not activated. It must be enabled for these two modes.
- The SQL Server Browser service must be launched.
|
| Mail server | - The workflow engine used in "Classic" mode requires an SMTP/POP3 server accessible from the server.
|
| Publication server | - An Apache server version 2.2 or later must be installed on the application server:
- Download link
- Select the no_ssl MSI installer package: httpd-2.2.25-win32-x86-no_ssl.msi.
|
| User accounts | - For the actual software users, it is recommended to define a user group and assign the access to the different software folders after the software component installation.
|
| Others | - A SAFE X3 ADXADMIN administration runtime must be installed on the server.
- A JDK or java runtime environment (version 8) must be installed.
- SSMS version 16.5.3 must be installed. Later versions should not be used.
- SAFE X3 Management Console CFG.239 must be installed.
|
SQL Server utility (for SQL server 2016)
From V12, the X3 Console and the X3 supervisor use the SQLCMD.exe SQL Server utility to:
- Check and retrieve the SQL Server instance characteristics during configuration through the X3 console.
- Create the SQL Server database in the SQL Server instance (when database creation is performed through the X3 Console).
- Create SQL Server users and schemas when importing a folder through the X3 Console, or when creating a new folder in the X3 Supervisor.
- Export sequence values when exporting folder data, and import sequence values when importing folder data.
- Perform various database verifications or management procedures in the X3 Supervisor.
From SQL Server 2016, this component is installed by a separate SQL Server Management Studio (SSMS) package.
The SSMS installation package is not delivered on the SQL Server 2016/2017 installation medium but a download link for this package is provided in the setup function.
If the SAFE X3 management console cannot find SQLCMD.exe, it rejects the installation environment, or it can use a SQL Server environment which may not be the correct one in the case of systems with multiple SQL Server versions.
For this reason, you have to make sure that SQLCMD.exe is located on all machines where you install and configure an X3 Runtime component (Main, Additional or Test). If you are using the default installation directory tree, you should find SQLCMD.exe in %ProgramFiles%\Microsoft SQL Server\Client SDK\ODBC\130\Tools\Binn or %ProgramFiles(x86)%\Microsoft SQL Server\Client SDK\ODBC\130\Tools\Binn.
If you are using SSMS 17.x, 130 can be replaced with 140 in the paths above.
Be cautious with the version of SQL Server Management Studio you are using.
With an SQL Server 2016 database, you should use SSMS 16.5.3 (the last SSMS 16 distribution) or SSMS 17.x (the latest being 17.9).
With an SQL Server 2017 database, you should use SSMS 17.9 or later.
Don't use mixed versions of SSMS (SSMS 17 installed over an existing SSMS 16 installation), this could confuse the console in the configuration procedure and lead to unexpected results.