Database versioning is the management and tracking of changes made to a database. All changes to scripts that define tables, procedures, triggers, views, indexes, sequences and other user defined objects are stored and versioned. Database versioning can also refer to the management and tracking of all database data where every Insert/Update/Delete operation is stored with intent to keep a permanent log of who performed which modifications.
Database versioning is the management and tracking of changes made to a database. All changes to scripts that define tables, procedures, triggers, views, indexes, sequences and other user defined objects are stored and versioned.
The date of the change, the user who made the change, and the content of that change is kept in a log for later review to enforce accountability for people making changes.
Database versioning can also refer to the management and tracking of all database data where every Insert/Update/Delete operation is stored with intent to keep a permanent log of who performed which modifications.
The purpose of database versioning is to assist in the detection and resolution of fraudulent or accidental modifications. With database versioning, hiding fraudulent modifications becomes more difficult. Without database versioning, accountability for who edited the database will be invisible and users committing fraudulent edits to the database can cover their tracks easily by making additional edits.
