The UniVerse Database: Version 11.2 released!

What do you get when you combine a NoSQL database with automatic data encryption, a fine-grained audit logging engine, account-based licensing and the ability to run SQL statements against a non-relational data store?

The leading industry Enterprise NoSQL solution that handles everything from core banking in hundreds of financial institutions to my luggage when I travel internationally, ticket bookings to emergency call dispatches and even showroom floor tablet-based sales apps.

To say I’m excited about release version 11.2 of the UniVerse database is an understatement. Let’s take a keep tour of just some of the new features available now:

Account-based licensing

This is a real boon for the multi-tenant environment, or for those who run multiple database account applications. It allows you to allocate license limits to individual accounts by simply modifying a configuration account.

Local subroutines/functions

This new language feature allows you to replace messy GOSUBs with a completely encapsulated subroutine or function in the same source file. It has been implemented in a manner that allows you to merely copy/paste external subroutines and functions at the end of your code. the CALL and CALL @ statements will now first check for a local version before checking the catalog spaces.

Replication Performance Monitoring

U2 Replication is the central pillar of a successful HA/DR setup for the UniVerse Database. The free XAdmin tool has been expanded with the ability to pinpoint where the bottlenecks are in your replication system. With 3 different views to cover buffer usage, data transmission and latency across the multiple stages of replication, you now know exactly where to look.

[box type=”download”]Free Download: U2 DBTools[/box]

Audit Logging

This big improvement for anyone in a heavily regulated industry (such as health care and financial services). It gives you an extremely fine-grained audit logging engine to make it easier to meet regulations such as HIPAA/HITECH and Sarbanes-Oxley. Audit logs are stored encrypted in a database protected file to prevent tampering. Along with this, a new U2 Basic function has been introduced so that you can pipe your own specific audit events directly into our audit logging engine, letting us taking care of the finer details and encryption.

Don’t forget to check out all our examples.