The following new features and enhancements are included in solidDB version 200.0.
Long in-memory rows
In solidDB version 200.0, the solidDB in-memory engine (M-tables) supports rows that are larger than 32KB in size.
In solidDB versions prior to 200.0, the M-table row size cannot not exceed the disk page size and is limited to 32KB, which prevents the insertion of large objects (CLOBs and BLOBs).
It is now possible to add M-table rows up to 32MB in size and for the memory row size to exceed the disk page size.
Long in-memory rows are enabled by default in solidDB version 200.0 and have a default value of 10MB. The value can be extended up to 32MB by modifying the solid.ini parameter MME.LongRowMaxLimit, see MME section.
Log writing optimizations
Log writing performance for the in-memory engine (M-tables) is optimized in solidDB version 200.0.
In solidDB versions prior to 200.0, each log file entry (insert/update/delete) writes the full row to the transaction log. For M-tables in solidDB version 200.0, the update and delete entries are optimized to write only the changed or minimally required data to the transaction log.
The data that is written to the transaction log always contains the primary key and unique key columns. If the optimization does not reduce the required data, the full record is written to transaction log.
This optimization only applies to M-tables. The solidDB Logreader requires full rows in the transaction log and disables the optimization if it is enabled.
The feature is automatically enabled.
OpenSSL 1.1.1 and offloading capabilities
solidDB version 200.0 supports OpenSSL 1.1.1. In addition to enhanced security, OpenSSL 1.1.1 includes the ability to offload cryptography to external devices. The offloading is vendor-specific and typically requires a custom OpenSSL library.
solidDB version 200.0 supports only TLS version 1.2.
OpenSSL is not provided as part of the solidDB package. You must either install OpenSSL or use the SSL libraries that are provided with the operating system. See Installing and configuring the OpenSSL toolkit.
If OpenSSLLibPath is not set, libssl.sharedlib and libcrypto.sharedlib must be set in LD_LIBRARY_PATH or LIBPATH (Linux and UNIX) or PATH (in Windows).
Running solidDB in containers
solidDB can run in Docker containers. Both glibc-based Linux images and Windows Nano servers are supported.
solidDB grid is an availability and scalability solution that runs in the cloud and in cloud-like environments. You can configure a set of solidDB servers, that run in multiple connected nodes, to appear as a single logical database.
