Abstract:
A tool for replacing a first database node of a database management system by a second database node. The tool receives an indication that the first database node received a data access request for accessing a database shared between the first database node and the second database node. The tool duplicates the data access request at the first database node. Responsive to a determination that the duplicated data access request includes a data changing statement and a previously executed statement, the tool modifies the duplicated data access request to prevent execution of the data changing statement and the previously executed statement at the second database node. The tool executes the modified duplicated data access request at the second database node. The tool replaces, based on a replacement condition being met, the first database node with the second database node in the database management system.
Abstract:
Various ways of storing data in tabular form such that some records are stored in a row oriented manner and some data is stored in a column oriented manner. The records respectively stored in the row and column oriented manners may, or may not, overlap (in whole or in part. Some embodiments accomplish this dual orientation of data by: (i) using a range partition; (ii) using a union all view command; and/or (iii) using a first table, a staging table and a materialized query table.
Abstract:
A system and method for a database management system. The method comprises: receiving a database transaction for inserting a set of records in a database table of the database management system or for creating indexes. The database transaction may be executed using the database management system. The database management system may rollback the database transaction by truncating the database table or the created indexes.
Abstract:
Various ways of storing data in tabular form such that some records are stored in a row oriented manner and some data is stored in a column oriented manner. The records respectively stored in the row and column oriented manners may, or may not, overlap (in whole or in part. Some embodiments accomplish this dual orientation of data by: (i) using a range partition; (ii) using a union all view command; and/or (iii) using a first table, a staging table and a materialized query table.
Abstract:
Embodiments related to processing of restricted-access data. An aspect includes receiving a request for data from a user by a storage system infrastructure comprising a centralized database that stores non-restricted access data and a local system that stores restricted-access data associated with a first set of areas or entities and comprising a federated database for providing a federated view, wherein the requested data comprises restricted-access first data and non-restricted access second data. Another aspect includes based on an association of the user, routing, by a routing entity, the request to the local system. Another aspect includes receiving the request at the at least one federated database of the local system. Another aspect includes retrieving from the federated database the restricted-access first data and the non-restricted access second data. Another aspect includes displaying the federated view comprising the restricted-access first data and the non-restricted access second data to the user.
Abstract:
Various ways of storing data in tabular form such that some records are stored in a row oriented manner and some data is stored in a column oriented manner. The records respectively stored in the row and column oriented manners may, or may not, overlap (in whole or in part. Some embodiments accomplish this dual orientation of data by: (i) using a range partition; (ii) using a union all view command; and/or (iii) using a first table, a staging table and a materialized query table.
Abstract:
Methods for capturing temporary database tables for analyzing a database query are provided. Aspects include obtaining a capture pattern and the database query having a sequence of statements. Aspects also include determining that a first statement of the sequence of statements matches the capture pattern, creating a list of temporary tables based on the first statement, and determining that a second statement of the sequence of statements includes one of a drop, commit, and truncate commands that correspond to a table in the list of temporary tables. Aspects further include creating a copy of the table in the list of temporary tables, generating an updated first statement by replacing a reference to the table in the list of temporary tables with a reference to the copy of the table, removing the table from the list of temporary tables, and executing the database query by performing the sequence of statements.
Abstract:
In several aspects for storing a table, in which the table is configured for comprising records having values of one or more attributes, a processor creates a pseudo table representing the table, the creating comprising defining an empty version of the table in a program. One or more records may be inserted in the pseudo table by encoding attribute values of the one or more records as inline data in the program. In response to determining that the pseudo table satisfies a materialization criterion, the pseudo table may be materialized by creating the table with the records encoded in the program and removing the program.
Abstract:
Various ways of storing data in tabular form such that some records are stored in a row oriented manner and some data is stored in a column oriented manner. The records respectively stored in the row and column oriented manners may, or may not, overlap (in whole or in part. Some embodiments accomplish this dual orientation of data by: (i) using a range partition; (ii) using a union all view command; and/or (iii) using a first table, a staging table and a materialized query table.
Abstract:
Embodiments related to processing of restricted-access data. An aspect includes receiving a request for data from a user by a storage system infrastructure comprising a centralized database that stores non-restricted access data and a local system that stores restricted-access data associated with a first set of areas or entities and comprising a federated database for providing a federated view, wherein the requested data comprises restricted-access first data and non-restricted access second data. Another aspect includes based on an association of the user, routing, by a routing entity, the request to the local system. Another aspect includes receiving the request at the at least one federated database of the local system. Another aspect includes retrieving from the federated database the restricted-access first data and the non-restricted access second data. Another aspect includes displaying the federated view comprising the restricted-access first data and the non-restricted access second data to the user.