Open topic with navigation
NuoDB 3.4.1 includes the following new features:
NuoDB systems managed by NuoDB Admin (
nuoadmin) now require a license key to enable the Enterprise Edition of NuoDB. For more information, see Obtaining and Installing an Enterprise Edition License.
NuoDB 3.4 includes the following new features:
NuoDB now fully supports transactional DDL statements. As a result, all metadata changes can be either fully committed or rolled back as a single logical unit along with any DML statements executed in the transaction. For general information on transaction behavior, see About Default Transaction Behavior.
To provide DDL behavior similar to the DDL behavior in an Oracle database, a new
AUTOCOMMIT_DDL system property is available. For more information on
AUTOCOMMIT_DDL, see SQL System Properties.
NuoDB Transaction Engines (TEs) now have the ability to store temporary data on disk to improve performance and reduce memory utilization for certain operations. For memory-intensive queries using the
ORDER BY clause, Spill to Disk functionality enables offloading of the intermediate results to disk on TEs. This allows NuoDB to efficiently process large, memory-intensive queries without impacting the performance of operational queries.
The Spill to Disk feature can also be use to reduce the time required to create indexes on large tables.
For more information, see Spill to Disk.
NuoDB supports new network encryption ciphers for Storage Managers (SMs), Transaction Engines (TEs), admin services, and JDBC, C, and C++ client drivers, as well as command-line tools such as NuoDB SQL. For information, see Network Encryption.
ALTER TRIGGER statement has been extended to support enabling, disabling, or reordering DDL triggers. For more information, see ALTER TRIGGER.
max-client-connections TE start-up option is available. This means that is now possible to specify a maximum number of client connections per Transaction Engine process. For more information, see Database Options.
A new management client package is available which enables the client management of a NuoDB database without the need to install the full NuoDB product on a client machine. For installation instructions, see the pynuoadmin page on the PyPi website. For usage details, see Management Client Package Setup.
It is now possible to configure more than one admin service process to perform bootstrap (initial start-up) of the domain. This allows better resiliency for new databases processes to enter the domain. For more information, click one of the following links:
Configuring NuoDB Admin Start-up (if you are using NuoDB Admin in a physical or VMware environment)
Configuring NuoDB Admin Start-up (if you have deployed NuoDB using OpenShift)
A new database provisioning operator has been published to the Red Hat Container Catalog that will allow Red Hat OpenShift customers to easily deploy a Community Edition (CE) of NuoDB using Red Hat Openshift 3.11 or greater. For more information, see the Red Hat Container Catalog.
nuocmd diagnostic subcommands are available for outputting database process connectivity information in either a JSON-suitable format for further analysis, or a table format that displays NuoDB domain and database active process connections. For more information, see Collecting Diagnostics.
nuoarchive command now supports the restoration of a specific incremental backup, rather than only being able to restore the most recent incremental backup. For more information, see Restoring to Specific Backup Elements.
nuoarchive command has been extended to remove failed transactions, from the TRANSACTIONS table, in databases that do not use Storage Groups. In the rare event that there are a large number of inserts made by failed transactions, removing failed transactions can improve query performance. For information on using the
nuoarchive command, see NuoDB Archive.
Two new logging categories are available. For more information on
record-reuse, see Description of Logging Categories.