Abstract: A system to synchronize a database and a non-database resource includes an application to transmit a request to a service provider to perform an action. The service provider receives the request and performs the action, the action not being under commit coordination. The service provider further inserts an entry into an action-reversal table to reverse the action and makes the insertion permanent. The service provider, on behalf of the application, then deletes the entry from the action-reversal table. The application may then be configured to perform one of the following: (1) make the delete permanent by performing a COMMIT; and (2) roll back the delete by performing a ROLLBACK. At a later time, the service provider may reverse the action in the event the entry remains in the action-reversal table. Corresponding methods and articles of manufacture (i.e., computer-readable media) are also disclosed herein.

Abstract: A system to synchronize a database and a non-database resource includes an application to transmit a request to a service provider to perform an action. The service provider receives the request and performs the action, the action not being under commit coordination. The service provider further inserts an entry into an action-reversal table to reverse the action and makes the insertion permanent. The service provider, on behalf of the application, then deletes the entry from the action-reversal table. The application may then be configured to perform one of the following: (1) make the delete permanent by performing a COMMIT; and (2) roll back the delete by performing a ROLLBACK. At a later time, the service provider may reverse the action in the event the entry remains in the action-reversal table. Corresponding methods and articles of manufacture (i.e., computer-readable media) are also disclosed herein.

Abstract: A method, system, and computer program product for determining storage locations for data objects is provided. The method includes providing user-selectable options for assigning storage locations for data objects, which is based upon a minimum threshold size of the data objects defined for a storage group. The options are implemented via a binary large object storage structure (LSS)-enablement indicator. The storage locations are further defined by a view associated with storage groups within an administrative table. Upon receiving a request to store a data object that exceeds the minimum threshold size, the method includes retrieving the selected options from the LSS-enablement indicator. If the LSS-enablement indicator is enabled for a portion of the storage groups, the method includes determining whether a view for the data table of the second storage subsystem for the assigned storage group exists via the administrative table. If the view exists, the data object is stored in the second storage subsystem.