A database system comprising a database having a dynamic schema and comprising a plurality of data storage nodes; and at least one processor configured to, using an encryption process: manage access to plaintext data stored in the plurality of data storage nodes by users employing at least one client-controlled resource in a client access layer; restrict access to the plaintext data by other users, wherein the other users include users with system administration privileges for the database and administrators of processing resources hosting the database; and manage access to encrypted copies of the plaintext data by the users with system administration privileges for the database such that the system administration privileges do not enable access to plaintext versions of the encrypted copies. A method for managing data security for a database. A database system with a dynamic schema architecture, a client access layer, and an operational database layer.

Systems and computer-implemented methods select a subset of methods to generate data schemas for input data from a list of methods for generating data schemas, based on output of a regression model; generate a candidate schema for each method in the subset of methods to generate data schemas; and generate a master data schema for the input data by merging the candidate schema for each method in the subset of methods to generate data schemas, utilizing predetermined rules.

Techniques are provided for analyzing events incoming through a message broker and configuring a database schema for storing the events based on the analysis. The analysis is performed on all the attributes of the incoming events with reference to a primary identifier of an event source. The analysis determines the characteristics of the attributes, which facilitates development of the database schema with availability, accuracy, existence, and other factors of various attributes. Analysis is supported for various formats of events, such as AVRO, XML, complex JSON, etc. In some examples, the attributes of interest for database schema generation can be provided via a configuration for the respective databases including relational, time-series, analytical, graph, etc. Also, if a given database supports direct ingestion of data through the message broker, then the ingestion specification can be generated.

Versions of a schema may be maintained for application to hierarchical data structures. Updates to include in a new version of a schema may be received. The updates may be evaluated for compatibility with a current version of the schema. Compatible updates may be included in the new version of the schema. Incompatible updates may not be included in the new version of the schema. The new version of the schema may be made available for application to hierarchical data structures inclusive of the compatible updates to the schema.

A computer implemented method for creating and managing a database system comprising data structures for storing, in a memory, data and relations between the data, the method comprising the steps of creating a mind map structure wherein each node of the mind map represents a set in the first data structure and each branch represents a relation in the fifth data structure of the database in which there are defined five data structures that hold all information relating to tables, records and relations, namely: a first data structure comprising a definition of at least one data set, a second data structure comprising definitions of properties of objects, a third data structure comprising definitions of objects, a fourth data structure comprising definitions of properties of each object, a fifth data structure comprising definitions of relations and a sixth data structure for storing definitions of relations between objects.

A method may include receiving, at a data lake platform, a packet including a metadata corresponding to a data schema of a source system. A change in the data schema of the source system may be detected based on a first checksum of the metadata and a second checksum of a previous version of the metadata. In response to detecting the change in the data schema of the source system, the metadata may be sent to a target system to enable the target system to perform, based on the data schema of the source system, a task operating on a data from the source system. The task may include reporting, visualization, advanced analytics, and/or machine learning. Related systems and computer program products are also provided.

Systems and methods for generating database schema change documents based on a data model and model changes indicated by a user. Information items related to one or more objects defined in the data model are received, and user input regarding changed objects is requested. In embodiments, changes are evaluated against configurable design criteria. One or more human and/or machine readable database schema change documents, and are stored in memory. Design criteria and change documents can vary based on a target database platform in embodiments.

A system for processing database data includes an interface and a processor. The interface is configured to receive a query for the database data comprising a date range and a data selection criterion. The processor is configured to determine a set of fields of the database data corresponding to a most recent date of the date range; determine a subset of the set of fields of the database data specified by the data selection criterion; determine a set of transformations, where each transformation of the set of transformations corresponds to a field of the subset and a sub-range of the date range; transform the database data to determine transformed database data using the set of transformations; and select data from the transformed database data using the data selection criterion to determine a query response.

Techniques for implementing tenancy isolation for entities are disclosed. In some embodiments, a computer system performs operations comprising: compiling a software project having one or more source code files, the source code file(s) comprising entity classes, each one of the entity classes having a corresponding entity class definition comprising a tenancy isolation annotation that is defined in a software library, the compiling of the software project comprising compiling the entity classes; and enhancing the compiled entity classes based on the entity class definitions of the compiled entity classes comprising the tenancy isolation annotation, the enhancing the compiled entity classes comprising adding a tenancy filter to the corresponding entity class definitions of the compiled entity classes, the tenancy filter being configured to apply tenancy isolation to entity instances of the compiled entity classes in a relational database.

As typical databases evolve and the schema defining the stored data changes, difficulties arise in interfacing with the database and compatibility to applications may be lost. Provided for are methods for retrieving data stored in a database using versioned reference perspectives of edges, which define relationships between nodes. The methods provide for backwards-compatibility in accessing node-data stored in accordance with a pre-defined schema based upon a request including a version identifier. Also provided for are backend systems, frontend systems, and industrial machines for the manipulation of work products.