Abstract: Embodiments provide a multi-buffering system in an application layer to support unified read/write access to different data source types of an underlying database layer. In a particular embodiment, the database layer comprises both a multi-dimensional data source (e.g. a cube), and another data source type (e.g. a Data Store Object—DSO). An abstract buffer component of the multi-buffering system is specialized into a delta buffer configured to read/write data of the cube, and into an after image buffer configured to read/write data of the DSO. A storage mechanism component of the multi-buffering system is specialized into a cache store configured to read/write data of the cube, and a calculation scenario store configured to read/write data of the DSO. The after image buffer may support certain aggregation rules during a DSO read/write operation. The calculation scenario store may leverage capabilities of an in memory database during a DSO read/write operation.

Abstract: Embodiments provide a multi-buffering system in an application layer to support unified read/write access to different data source types of an underlying database layer. In a particular embodiment, the database layer comprises both a multi-dimensional data source (e.g. a cube), and another data source type (e.g. a Data Store Object—DSO). An abstract buffer component of the multi-buffering system is specialized into a delta buffer configured to read/write data of the cube, and into an after image buffer configured to read/write data of the DSO. A storage mechanism component of the multi-buffering system is specialized into a cache store configured to read/write data of the cube, and a calculation scenario store configured to read/write data of the DSO. The after image buffer may support certain aggregation rules during a DSO read/write operation. The calculation scenario store may leverage capabilities of an in memory database during a DSO read/write operation.

Abstract: Embodiments relate to methods and apparatuses implementing database-level consistency checking in a declarative manner. A consistency engine within the database layer may access one or more consistency rules in the form of a table or executable program code. Based upon application of these consistency rules to records comprising combinations of data characteristics, the consistency engine may determine the validity or invalidity those records. Consistency rules may implement a ‘check’ method, and also a ‘derive’ method allowing derivation of data characteristics (targets) in a record from other characteristics (sources) in the record. Filters may be used to split data records to sets of records having all fields assigned, and those having ‘not assigned’ fields. Consistency rules used for derivation methods can be nested. Also, in certain embodiments a consistency engine may use filtering techniques for constraint checking including multi-level derivations in a declarative way.