Menu
This document describes the Deployment, Installation, Back-out, and Rollback Plan for new products going into the VA Enterprise. The plan includes information about system support, issue tracking, escalation processes, and roles and responsibilities involved in all those activities. Having a strong rollback plan has changed the way we do releases. We have not needed it very often, but when we did it was a lifesaver. We are no longer live in fear of bad deployments and are confident we can get back to a working state quickly and easily. With a little bit of planning and effort we now have a rollback plan that is: Automated.
The items contained in Performing General Software Development Activities, Section 4, identify basic topics that are necessary to create a workable plan for a software project. When a significant change occurs in the approach to software development, this plan must be updated to reflect that change. A backout plan is a contingency plan component of the IT service management framework. It is implemented prior to any software or system upgrade, installation, integration or transformation to ensure automated system business operations, should a new system fail to deliver not clear post-implementation testing. The Installation, Back-out, Rollback Plan defines the ordered, technical steps required to install the product, and if necessary, to back-out the installation, and to roll back.
In database technologies, a rollback is an operation which returns the database to some previous state. Rollbacks are important for database integrity, because they mean that the database can be restored to a clean copy even after erroneous operations are performed. They are crucial for recovering from database server crashes; by rolling back any transaction which was active at the time of the crash, the database is restored to a consistent state.
The rollback feature is usually implemented with a transaction log, but can also be implemented via multiversion concurrency control.
Cascading rollback[edit]
A cascading rollback occurs in database systems when a transaction (T1) causes a failure and a rollback must be performed. Other transactions dependent on T1's actions must also be rollbacked due to T1's failure, thus causing a cascading effect. That is, one transaction's failure causes many to fail.
Software Development Rollback Plan 2017
Practical database recovery techniques guarantee cascadeless rollback, therefore a cascading rollback is not a desirable result.
SQL[edit]
SQL refers to Structured Query Language,a kind of language used to access,update and manipulate database.In SQL,
ROLLBACK
is a command that causes all data changes since the last BEGIN WORK
, or START TRANSACTION
to be discarded by the relational database management systems (RDBMS), so that the state of the data is 'rolled back' to the way it was before those changes were made.Software Development Rollback Plan Free
A
ROLLBACK
statement will also release any existing savepoints that may be in use.In most SQL dialects,
ROLLBACK
s are connection specific. This means that if two connections are made to the same database, a ROLLBACK
made in one connection will not affect any other connections. This is vital for proper concurrency.See also[edit]
References[edit]
- Ramez Elmasri (2007). Fundamentals of Database Systems. Pearson Addison Wesley. ISBN0-321-36957-2.
- 'ROLLBACK Transaction', Microsoft SQL Server.
- 'Sql Commands', MySQL.
Retrieved from 'https://en.wikipedia.org/w/index.php?title=Rollback_(data_management)&oldid=899956161'