SQL/R A.03.00 Release Notes
Welcome to the SQL/R A.03.00 release.SQL/R provides SQL access to the Eloquence database.
-
The SQL/R ODBC Driver enables easy and transparent access to the
Eloquence database from ODBC aware applications.
- The SQL/R Report Generator provides an easy and flexible method to create reports on the fly, based on the SQL database query language.
Note that the above two SQL/R product options are licensed separately.
The SQL/R A.03.00 release implements a number of enhancements.
- Encrypted communication
SQL/R A.03.00 adds a secure network protocol, using an RSA encrypted key exchange method and AES session encryption key. - LDAP support
SQL/R A.03.00 adds the LDAP user authentication method. -
SQL/R A.03.00 supports the Eloquence database audit functionality.
The ODBC driver submits login, user and process audit information
through the SQL/R server to the Eloquence database server.
- Encrypted passwords
SQL/R A.03.01 adds support for storing passwords in an encrypted form. -
SQL/R A.03.01 adds support for groups (security = ODBC and LDAP).
- Linux systemd support
As of A.03.21, SQL/R on the Linux platform preferably uses systemd to manage services, where available. - FTS index support
SQL/R A.03.30 adds support for Eloquence FTS indexes. -
SQL/R A.03.32 adds support for multiple sqlrodbcd instances.
- SQL/R A.03.33 introduces IPv6 support.
The current SQL/R A.03.00 version is A.03.33 (A.03.35 beta test).
Fixed Problems and Recent Changes
Installation and Upgrade
Please refer to the SQL/R A.03.00 installation documents below for an overview of SQL/R installation and platform specific details, as well as information on updated License Keys.
SQL/R A.03.00 license key
SQL/R A.03.00 requires a license key revision of A.03.00 or higher.
If an Eloquence Personal Edition is installed and no valid SQL/R license key is detected, a two user license is granted automatically.
To request a SQL/R license key, please contact sales@marxmeier.com.
ODBC driver backwards compatibility
The SQL/R A.03.00 ODBC server is fully backwards compatible to previous ODBC drivers. Consequently, updating the ODBC server side to A.03.00 server does not require updating all clients.The SQL/R A.03.00 client / ODBC driver by default uses a new network protocol which supports the encryption and auditing functionality. This protocol is not backwards compatible with previous SQL/R A.02.xx server versions.
To communicate with a previous SQL/R A.02.xx server, the SQL/R client / ODBC driver must be configured to use the backwards-compatible A02 network protocol.
The A02 network protocol is used:
-
if the environment variable SQLR_PROTOCOL=A02 is set
-
if the Protocol=A02; option in the ODBC connection string
is specified
-
if the Protocol=A02 option is specified in the data source
definition in the odbc.ini configuration file of the ODBC
driver manager
-
on the Windows platform, if the option to use the A02
network protocol is checked in the data source configuration
dialog
- on the Windows platform, if Protocol=A02 is configured in the [Config] section of the ODBC driver configuration file (Start Menu - Programs - SQLR - ODBC Driver Configuration).