Abstract: Provided are techniques for generating a Graphical User Interface (GUI) based on relationships between tables identified in a data model and displaying the GUI to enable selection of the tables and columns in the tables. Via the GUI, a selection of at least one of the tables and a selection of at least one of the columns in the at least one of the selected tables are received. A statement is generated based on the selected tables and the selected columns. The statement is executed to obtain results. The results are processed to create a data object having a hierarchical structure that indicates the relationships between the tables.

Abstract: Provided are techniques for generating a Graphical User Interface (GUI) based on relationships between tables identified in a data model and displaying the GUI to enable selection of the tables and columns in the tables. Via the GUI, a selection of at least one of the tables and a selection of at least one of the columns in the at least one of the selected tables are received. A statement is generated based on the selected tables and the selected columns. The statement is executed to obtain results. The results are processed to create a data object having a hierarchical structure that indicates the relationships between the tables.

Abstract: Provided are techniques for generating a Graphical User Interface (GUI) based on relationships between tables identified in a data model and displaying the GUI to enable selection of the tables and columns in the tables. Via the GUI, a selection of at least one of the tables and a selection of at least one of the columns in the at least one of the selected tables are received. A statement is generated based on the selected tables and the selected columns. The statement is executed to obtain results. The results are processed to create a data object having a hierarchical structure that indicates the relationships between the tables.

Abstract: Provided are techniques for generating a Graphical User Interface (GUI) based on relationships between tables identified in a data model and displaying the GUI to enable selection of the tables and columns in the tables. Via the GUI, a selection of at least one of the tables and a selection of at least one of the columns in the at least one of the selected tables are received. A statement is generated based on the selected tables and the selected columns. The statement is executed to obtain results. The results are processed to create a data object having a hierarchical structure that indicates the relationships between the tables.

Abstract: A system for efficient snapshot querying include: providing a first version value for each data in a history table, where the first version value indicates a beginning of a period in which the data is valid; providing at least a second version value for each data in the history table, where the second version value indicates an end of the period in which the data is valid; receiving a request for a version of a database; and retrieving the data with the first version value less than or equal to the requested version and the second version value greater than or equal to the requested version. By maintaining a history table with redundant version information, the system is able to provide efficient snapshot querying while also avoiding the overhead burden of conventional approaches. No aggregates, joins, or sub-queries are required to retrieve a snapshot.

Abstract: A system for synchronizing data on a first device with data at a second device, includes: determining a pre-image of the data on the first device according to a filter after a previous synchronization with the data at the second device; determining a current image of the data at the second device according to the filter; determining a delta of the current image, where the delta comprises data that exists in the current image and has changed since the previous synchronization; instructing the first device to delete data that exists in the pre-image but not in the current image; and instructing the first device to UPSERT a union of the data that exists in the delta and the data that exists in the current image but not the pre-image. This is efficient in time and bandwidth resources while also providing consistent data integrity.

Abstract: A method and system for efficient snapshot querying include: providing a first version value for each data in a history table, where the first version value indicates a beginning of a period in which the data is valid; providing at least a second version value for each data in the history table, where the second version value indicates an end of the period in which the data is valid; receiving a request for a version of a database; and retrieving the data with the first version value less than or equal to the requested version and the second version value greater than or equal to the requested version. By maintaining a history table with redundant version information, the method and system are able to provide efficient snapshot querying while also avoiding the overhead burden of conventional approaches. No aggregates, joins, or sub-queries are required to retrieve a snapshot.

Abstract: A system for efficient snapshot querying include: providing a first version value for each data in a history table, where the first version value indicates a beginning of a period in which the data is valid; providing at least a second version value for each data in the history table, where the second version value indicates an end of the period in which the data is valid; receiving a request for a version of a database; and retrieving the data with the first version value less than or equal to the requested version and the second version value greater than or equal to the requested version. By maintaining a history table with redundant version information, the system is able to provide efficient snapshot querying while also avoiding the overhead burden of conventional approaches. No aggregates, joins, or sub-queries are required to retrieve a snapshot.

Abstract: A system for synchronizing data on a first device with data at a second device, includes: determining a pre-image of the data on the first device according to a filter after a previous synchronization with the data at the second device; determining a current image of the data at the second device according to the filter; determining a delta of the current image, where the delta comprises data that exists in the current image and has changed since the previous synchronization; instructing the first device to delete data that exists in the pre-image but not in the current image; and instructing the first device to UPSERT a union of the data that exists in the delta and the data that exists in the current image but not the pre-image. This is efficient in time and bandwidth resources while also providing consistent data integrity.

Abstract: A method and system for synchronization-replication concurrency maintain a history table for a data table in a mirror, where the history table can include redundant version values that indicate a period in which data values corresponding to the version values are valid. Replication can thus be performed between a source and a mirror for a current version of the data table, while synchronization is simultaneously performed between the mirror and a client for an earlier version of the data table using the history table.

Abstract: A method for synchronizing data on a first device with data at a second device, includes: determining a pre-image of the data on the first device according to a filter after a previous synchronization with the data at the second device; determining a current image of the data at the second device according to the filter; determining a delta of the current image, where the delta comprises data that exists in the current image and has changed since the previous synchronization; instructing the first device to delete data that exists in the pre-image but not in the current image; and instructing the first device to UPSERT a union of the data that exists in the delta and the data that exists in the current image but not the pre-image. This is efficient in time and bandwidth resources while also providing consistent data integrity.