Hasso-plattner-institut Für Digital Engineering Ggmbh

Hasso-plattner-institut Fur Softwaresystemtechnik Gmbh

Matthias Uflacker

Hasso Plattner

Rainer Schlosser

Martin Boissier

Alexander Zeier

Jan Kossmann

Cafer Tosun

Janek Schumann

Kok Thim Chew

The inventors have implemented in a columnar in-memory database and studied access patterns of a large production enterprise system. To obtain accurate cost estimates for a configuration, the inventors have used the what-if capabilities of modern query optimizers. What-if calls, however, are the major bottleneck for most index selection approaches. Hence, a major constraint is to limit the number of what-if optimizer calls. And even though the inventive approach does not limit the index candidate set, it decreases the number of what-if calls because in each iteration step the number of possible (index) extensions is comparably small which results in a limited number of what-if calls.

Iterative multi-attribute index selection for large database systems

Computer-implemented method for allocating columns of a table stored in a database system into at least two sets of columns, a first set and a second set, the data of the columns allocated to the first set being stored on a primary storage medium using a column-oriented data structure and the data of columns allocated to the second set being stored on a secondary storage medium using a row-oriented data structure, wherein the method comprises the step of allocating the columns of the table to the first and the second set autonomously on the basis of a performance-cost model.

Data placement in hybrid data layouts for tiered HTAP databases

In one embodiment the present invention relates to a method for navigating within a database containing business objects. The method includes the steps of providing a preconfigured model comprising preconfigured business object types and preconfigured associations of the business object types, identifying a reference to a business object instance within a software object and determining a primary business object type corresponding to the business object instance, providing links to at least one secondary business object type associated with the primary business object type in accordance with the preconfigured business model, and retrieving from the database at least one attribute of at least one business object instance within the secondary business object type associated to the primary business object type in accordance with the preconfigured model. In this manner, a user may more easily navigate the database.

Business object based navigation

Growing community of inventors

Berlin, Germany

Matthias Uflacker