Abstract: Methods for replicating transactional tables of a transactional database to an analytical database and maintaining updates to those transactional table representations are disclosed. Snapshots of the transactional tables are provided to the analytical database via a transport mechanism, such as a data storage service or a data streaming service, and stored at the analytical database. Then, checkpoints comprising portions of a change-data-capture log that has recorded transactional changes to the transactional tables of the transactional database are provided to the analytical database via the same or different transport mechanism and used to commit those transactional changes to the snapshot representations. The snapshot representations may be used to respond to incoming analytical queries in order to provide real-time querying results.

Abstract: Methods for negotiating parameters for maintaining, at an analytical database, a replica of a transactional table, stored at a transactional database, are disclosed. By establishing parameters of said maintenance prior to commencing, the transactional database and the analytical database may remain only loosely coupled after completing the negotiation. The parameters of the negotiation may be stored in a location that is accessible to both the transactional database and the analytical database, such that the results of the negotiation may be accessed during the process of maintaining the replica. The negotiation may include a procedure to provide portions of a change-data-capture log, associated to the transactional table, to the analytical database via a transport mechanism such that the replica may be updated, in addition to a list of agreed upon data definition language commands that may be used in the portions of the change-data-capture log.

Abstract: Methods for implementing insert, update, and delete events of a change-data-capture log in transactional order to a representation of a transactional table are disclosed. Insert events may be applied and committed to the representation, while delete events may be buffered and committed to a shadow table. Such buffering may allow the delete events to be applied and committed as a batch to the given representation as a later background operation, allowing for an optimized application of the change-data-capture log to the representation. Once the delete events are committed to the representation, they are removed from the shadow table. Update events may be similarly treated in which the insert event component of the update event is applied and committed to the representation while the delete event component is committed to the shadow table, before being later committed to the representation and removed from the shadow table.

Abstract: Methods for negotiating parameters for maintaining, at an analytical database, a replica of a transactional table, stored at a transactional database, are disclosed. By establishing parameters of said maintenance prior to commencing, the transactional database and the analytical database may remain only loosely coupled after completing the negotiation. The parameters of the negotiation may be stored in a location that is accessible to both the transactional database and the analytical database, such that the results of the negotiation may be accessed during the process of maintaining the replica. The negotiation may include a procedure to provide portions of a change-data-capture log, associated to the transactional table, to the analytical database via a transport mechanism such that the replica may be updated, in addition to a list of agreed upon data definition language commands that may be used in the portions of the change-data-capture log.

Abstract: Methods for replicating transactional tables of a transactional database to an analytical database and maintaining updates to those transactional table representations are disclosed. Snapshots of the transactional tables are provided to the analytical database via a transport mechanism, such as a data storage service or a data streaming service, and stored at the analytical database. Then, checkpoints comprising portions of a change-data-capture log that has recorded transactional changes to the transactional tables of the transactional database are provided to the analytical database via the same or different transport mechanism and used to commit those transactional changes to the snapshot representations. The snapshot representations may be used to respond to incoming analytical queries in order to provide real-time querying results.

Abstract: Methods for implementing insert, update, and delete events of a change-data-capture log in transactional order to a representation of a transactional table are disclosed. Insert events may be applied and committed to the representation, while delete events may be buffered and committed to a shadow table. Such buffering may allow the delete events to be applied and committed as a batch to the given representation as a later background operation, allowing for an optimized application of the change-data-capture log to the representation. Once the delete events are committed to the representation, they are removed from the shadow table. Update events may be similarly treated in which the insert event component of the update event is applied and committed to the representation while the delete event component is committed to the shadow table, before being later committed to the representation and removed from the shadow table.

Abstract: Techniques for resizing a distributed database are described. A request to resize a distributed database is received. The distributed database stores data organized into one or more rows of one or more tables. Each node of the first plurality of nodes is assigned a portion of the data. A portion of the data assigned to a first node in the first plurality of nodes is selected to be assigned to a second node in a second plurality of nodes. The number of nodes in the first and second plurality of nodes is different, and the first and second plurality of nodes include at least one common node. Metadata of the selected portion of the data is transferred from the first node to the second node. The metadata that includes a location of the selected portion of the data within a provider network.

Abstract: Described is an approach for computing a quorum for a two-node non-shared storage converged architecture via a distributed state machine without the need for a quorum device.

Abstract: Described is an approach for computing a quorum for a two-node non-shared storage converged architecture via a distributed state machine without the need for a quorum device.