Server database

The various estos UCServer services, such as telephony, calendar, scheduled calls and chat, use a database. Microsoft Access® or Microsoft SQL Server® (since version 2000) can be used.

Microsoft Access® is recommended only for smaller installations with up to 25 users.
An SQL Server® installation should be used for more users and/or to fulfill stricter security policies.

When changing the server database (esp. from Microsoft Access® to Microsoft SQL® Server) the general notices for the SQL database do apply.
On a change no data will be transfered. Data of the previously used database will remain entirely.

Microsoft Access®

Microsoft Access® Databases are files created on the estos UCServer computer.

  • Directory
    The absolute path to the directory where the database has been stored. If this path will be changed and existing data should not be lost, the existing database must first be copied into the new directory. The path is an absolute path to the computer running the estos UCServer service. If a connection should be made to a estos UCServer remote computer using estos UCServer Administration, access to the other computer’s file system will not be available. In that case, the indicated path is a local path to the computer targeted by the connection.

The Microsoft Access® ODBC database drivers must be installed on the computer. This will be checked during the server setup and if necessary the drivers will be installed. To install these drivers manually on 64 bit systems, execute the command 'AccessDatabaseEngine_X64.exe /passive’ in the installation directory under 'Supportfiles’. This installs the 'Microsoft Access® Database Engine 2010 Redistributable’.

Microsoft SQL Server®

The following configuration is required for operating SQL Server®:

  • Server name
    Enter the name or the IP-address of the server here. If a named instance, such as an SQL Server® Express installation, should be used, the name of the instance must also be specified. Such names will follow the pattern: HOSTNAME\INSTANCENAME.
    For example: hostname\SQLExpress
  • Authentication
    estos UCServer supports the following options for authentication.
    • Windows® Authentication using a Service Account
      estos UCServer will implicitly log onto the SQL Server® using the Windows® user account that started the estos UCServer service. There will be no need to specify the user name and password in this case. For this authentication method, make sure that the service account running the estos UCServer instance will have access to the necessary access rights on the SQL server. By default, the local system account will be used for logging the estos UCServer installation on as a service account, which usually already has full access to a local instance of SQL Server® Express. estos UCServer and the SQL Server® must run on the same machine when using the local system account. The estos UCServer service must be converted from using the local system account to using a Windows® account with network permissions for using Windows® Authentication using a Service Account and an SQL Server® that will be accessed through the network. The service account can be converted by opening the service from the Control Panel and the Administrative Tools and setting the desired Windows® user account from the properties for the estos UCServer entry.
    • Windows® Authentication
      If Windows® authentication has been selected, a Windows® user account with password must be explicitly specified, which the estos UCServer service will use for logging onto SQL Server®. For this authentication method, make sure that the specified Windows® user account has the necessary access rights for the SQL Server®.
    • SQL Server® authentication
      If SQL Server® authentication has been selected, the user account setup in SQL Server® will be used to log onto the database. SQL Server® must have activated the setting for the so-called Mixed Mode for this. For this authentication method, make sure that the specified SQL Server® user account has the necessary access rights for the SQL Server®.
  • User name and Password
    Enter the login information that estos UCServer should use for logging onto SQL Server®. The user name and password cannot be entered for all types of authentication. For Windows® authentication enter the fully qualified user name as the user name, meaning for example "user@domain". Alternatively, the Windows® login notation ("domain\user") can also be used.
  • Database name
    Enter here the database name where estos UCServer should store its data. estos UCServer will manage the necessary tables itself. The already existing databases will be provided for selection once the connection with the SQL Server® has been successfully setup. Setting up a dedicated database for estos UCServer is recommended. If a database not in the list is specified, it will be created if the specified user has the required access rights.

Further instructions for connecting to SQL Server® and SQL Server® Express

Context Solution
UCServer will start during system startup before the database service. If SQL Server® has been installed on the same computer as UCServer, the database service must be started first. This can be controlled through the service dependences. To accomplish this, the SC.exe service control program can be run from the command line. For example, using the command:
sc config ectisrv depend= MSSQL$SQLEXPRESS/TapiSrv/LmHosts
says that ECTISRV is dependent on the MSSQL$SQLEXPRESS database service, the TapiSrv TAPI sub-system and the network layer, must be started first, when they are running.
The sc /? command will provide additional help about sc.exe.
Note: a space should be entered after the equals sign in the parameter "depend=".
Authentification and access rights Apart from read and write access the estos UCServer needs the following rights for accessing the database:
  • Create database
    When the server starts the configuration for the first time it attempts to create the database if it does not yet exist.
    If the database already exists the right is not used.
  • Create table
    When the server starts the configuration for the first time the required tables are created in the specified database if they do not yet exist.
    If the tables already exist the right is not used.
  • Change tables
    It is possible (although seldom) that the introduction of new features or improvements will make it necessary to change (add to) tables.
    At start-up the server analyzes the table structure and automatically makes extensions and changes.
    If such a procedure is necessary, the instructions will be noted in the release notes and the necessary changes will be described there.
These rights are not required if the corresponding works or changes are done by hand.

Version 6.0