The Express edition is a standalone application that is used by a single user. It's primarily used in small to medium organizations (SMBs) and is limited to handling databases of up to 500 tables. The Enterprise editoin is a multi-user client/server solution, to be used in medium-to-large organizations. As fully-fledged enterprise software, this edition is shipped with a built-in job scheduler, flexible notification system, web-service API, and more.

When you encrypt database data, it becomes unreadable and unrecognizable by both the application and the user. However, scrambling data ensures it is readable by a user and meaningful to the application, without compromising privacy. For example, a credit-card number of "4444-6666-7777-9999" may look like “mM2A2M48(OiikdsOW” after it is encrypted. This is meaningless both to an application and a user. However, the same value may be scrambled into a (valid) credit-card number of “6565-8899-1002-2222” that can be used in non-production databases, without compromising the customer’s private data.

Database best practices dictate setting of Primary-Keys and Foreign-Keys to ensure referential data integrity. However, in many real-life environments, Foreign-Keys are not defined leaving the application responsible for maintaining referential data integrity. In common business scenarios, a non-developer (e.g. security administrator, DBA, architect) is asked to determine the referential relations between database tables. Unfortunately, in the lack of foreign-keys this may become an arduous task. JumbleDB Enterprise can bridge this gap by detecting application referential integrity relations, which are not defined in the database.

Not in the current version. However, this feature is on our wish-list and will be supported in a future version.

Yes. JumbleDB Enterprise may locate values inside large text fields, for all supported RDBMS.