Database considerations
All platformsβ
Determine which database type(s) you want to use.β
Refer to the Database section for more information related to the database types compatible with SoftExpert Suite.
Note that SQL scripts will be executed during the installation process.β
A series of SQL scripts will be executed to create the objects in the database and insert the configuration data. These scripts are executed automatically by the SoftExpert Suite installation tool. The SoftExpert Suite installation will be completed only if these scripts are executed successfully.
SQL Serverβ
Set up SQL Server Collationβ
The collations that may be used in western languages for the SoftExpert Suite database in SQL Server are:
SQL_Latin1_General_CP1_CI_AS
SQL_Latin1_General_CP1_CI_AI
Latin1_General_CI_AS
Latin1_General_CI_AI
The CI (Case Insensitive) parameter of the collation must always be used. We recommend using the AIΒ (Accent Insensitive)Β parameter for new databases, as of 2.1. For eastern languages, contact SoftExpert Support.
For TLS 1.2 connections to SQL Server database, certain requirements may be necessary. The installation and update guides have further information on those requirements.
It is important to be aware of the Express version limitations. See further details in the Servers > Database section.
READ_COMMITTED_SNAPSHOT
isolation level configurationβ
In order to prevent locks and deadlocks in reading operations performed in the SoftExpert Suite database, it is possible to use isolation by Snapshot, which will version each record in the tempdb. More information at http://msdn.microsoft.com/en-us/library/ms173763.aspx.
To enable this parameterization, run the commands below, without having any
active connection in the <database>
:
ALTER DATABASE <Database> SET ALLOW_SNAPSHOT_ISOLATION ON;
ALTER DATABASE <Database> SET READ_COMMITTED_SNAPSHOT ON;
Oracleβ
Determine your NLS and character-set requirementsβ
As of version 2.0.13, SoftExpert Suite supports the WE8MSWIN1252
(non-unicode)
and AL32UTF8
(unicode) character sets. However, we advise using AL32UTF8
only when there is a need for languages that cannot be saved in the non-unicode
format.
Determine the Oracle client NLSβ
After defining the character set to be used by the Oracle database server, you
must define the NLS_LANG
environment variable for the client installations
that will connect to the server. The environment variable must be in line with
the character set of the server. In an environment where the server is running
with WE8MSWIN1252
, for example, it is common to use the NLS_LANG
set up with
AMERICAN_AMERICA.WE8MSWIN1252
.
Create/manage your tablespacesβ
SoftExpert Suite uses one tablespace for data, and one for indexes. The size required for an initial installation should be 2GB (data) and 200MB (indexes). These numbers tend to increase as the features of the tool are used, especially when documents are added through the SoftExpert Document component or forms. Therefore, tablespace growth must be constantly monitored, and ensuring that there is size available for it is required.
Important: We recommend using a controlled directory to store the files, which helps slow down database growth.
PostgreSQLβ
Determine your encoding requirementsβ
Server and client require en_US.UTF-8
encoding for all languages.
ATTENTION
- The Postgres database must necessarily use the
en_US.UTF-8
collate, exclusively, in order to ensure compatibility with SoftExpert Suite.
Network configurationβ
To access the PostgreSQL server, you must enter the customer's network
configurations in the pg_hba.conf
file and enable external access in the
postgresql.conf
file (the PostgreSQL service must be restarted). Refer to the
"SoftExpert Suite - Installation Guide" document, "Database configuration"
section
(Linux
or
Windows)
for information on the PostgreSQL network configuration.