Newness and distinctiveness is claimed in the features of ornamentation as shown inside the broken line circle in the accompanying representation.

Display screen or portion thereof with graphical user interface

A hybrid database table is stored as both a row and a column store. One or more techniques may be employed alone or in combination to enhance performance of the hybrid table by regulating access to, and/or the size of, the processing-intensive column store data. For example during an insert operation, the column store data may be searched for a uniqueness violation only after certain filtering and/or boundary conditions have been considered. In another technique, a hybrid table manager may control movement of data to the column store based upon considerations such as frequency of access, or underlying business logic. In still another technique, querying of the hybrid table may result in a search of the column store data only after an initial search of row store data fails to return a result.

Hybrid database table stored as both row and column store

This system comprises methods that simplify the creation of multidimensional OLAP models from one or more semantically enabled data sources. The system also comprises methods enabling interoperability between existing OLAP end-user interfaces, the system's representation of OLAP and the underlying data sources. This includes web-enabled OLAP interfaces.

Automatic synthesis and presentation of OLAP cubes from semantically enriched data sources

As part of a database system comprising a combination of on-disk storage and in-memory storage, a plurality of records that comprise a table are stored in a plurality of fragments that include at least a delta fragment and a main fragment retained in the on-disk storage. Each fragment has visibility data structures to enable multi-version concurrency control. Each fragment can be compressed using dictionary compression and n-bits compression. The fragments are loaded into main system memory in the in-memory storage from the on-disk storage if they are accessed for read operations or write operations and are not already in memory. A plurality of lockless read and write operations are concurrently performed, while providing snapshot isolation, on the at least one of the plurality of fragments while the at least one of the plurality of fragments is in the main system memory.

In-memory database system providing lockless read and write operations for OLAP and OLTP transactions

Various techniques are described for platform management of integrated access of public and privately-accessible datasets utilizing federated query generation and query schema rewriting optimization, including receiving at a dataset access platform a query formatted according to a first data schema, generating a copy of the query, saving the query and the copy to a datastore, parsing the copy of the query in the first schema using an inference engine, determining whether the query comprises data associated with an access control condition associated with accessing the dataset, the access control condition being configured to indicate whether the query is permitted to access the dataset, and rewriting, using a proxy server, the copy of the query in a second schema, and optimizing the rewriting by identifying a database engine to execute the query and including other data converted into another triple associated with an attribute of the query.

Platform management of integrated access of public and privately-accessible datasets utilizing federated query generation and query schema rewriting optimization

A computer system provides access to both an online transaction processing (OLTP) database server and an online analytics processing (OLAP) database server. The computer system includes a client application adapted to receive a query. According to (a) mode of operation (e.g., read or update) of the client application and (b) synchronization status of the OLAP database server, the client application redirects the query to the OLTP database server or to the OLAP database server. The client application redirects the query to the OLTP database server when the mode of operation is other than a read-only operation or the synchronization status is "unsynchronized". The client application redirects the query to the OLAP database server when the mode of operation is a read-only operation and the synchronization status is "synchronized". The computer system further includes an OLTP application server (e.g., Enovia V6) comprising an OLTP adapter and an OLAP adapter. The OLAP adapter is formed of a mapping component adapted to map data between OLTP semantics and OLAP semantics.

Computer method and system for combining OLTP database and OLAP database environments

PROBLEM TO BE SOLVED: To provide transparent access to both OLTP and OLAP databases.SOLUTION: A client application redirects a query to the OLTP database server when a mode of operation of the client application is other than a read-only operation or a synchronization status of an OLAP database server is "not synchronized." The client application redirects the query to the OLAP database server when the mode of operation is a read-only operation and the synchronization status is "synchronized." The computer system further includes an OLTP application server comprising an OLTP adapter and an OLAP adapter. The OLAP adapter is formed of a mapping component adapted to map data between OLTP semantics and OLAP semantics.

David Edward Tewksbary

Papers

Computer method and system for combining OLTP database and OLAP database environments

Method and system for computer for combining oltp database environment and olap database environment