Abstract: A method, apparatus, system, and signal-bearing medium that in an embodiment, store a reason identifier in rows in a database. The reason identifier identifies the most recent change to the rows. The content of the rows that existed prior to the change are stored in journal records. In response to an undo command, the most-recent instance of each record identifier in the records associated with the reason identifier are found in the journal and moved to the database in reverse time sequence order. In an embodiment, a promote operation requests moving the change upwards in a sequence, from a source version to a target version of the database. In response to the promote operation, a determination is made whether rows with the same row identifiers but a different reason identifier exist in a target version of the database, but the different reason identifier is complete.

Abstract: Embodiments of the present invention provide an integrated methodology that simplifies upgrade choices for complex computer products through the use of automation and integration of product monitoring and business applications with, for example, web based capabilities. Historical information for computer systems is collected and transmitted to a remote support system. Over time, sufficient historical data provides a historical view of the systems indicative of usage and facilitating the choice of product enhancements, upgrades and customization. Further, this historical view may be integrated with the advances in the product that are kept by the remote support system as well as with the performance requirements of third party application providers.

Abstract: A method, apparatus, system, and signal-bearing medium that in an embodiment, store a reason identifier in rows in a database. The reason identifier identifies the most recent change to the rows. The content of the rows that existed prior to the change are stored in journal records. In response to an undo command, the most-recent instance of each record identifier in the records associated with the reason identifier are found in the journal and moved to the database in reverse time sequence order. In an embodiment, a promote operation requests moving the change upwards in a sequence, from a source version to a target version of the database. In response to the promote operation, a determination is made whether rows with the same row identifiers but a different reason identifier exist in a target version of the database, but the different reason identifier is complete.