Updating source control status
Math Works Machine Translation The automated translation of this page is provided by a general purpose third party translator tool.Math Works does not warrant, and disclaims all liability for, the accuracy, suitability, or fitness for purpose of the translation.So, given the many good reasons for using Version Control systems for managing the changes in database applications, how does one go about the rather different routines of team development, such as testing, continuous integration, and managing data? With this article, we begin our exploration of the processes, tools and practices that are required in order to allow a team of developers, or even several teams of developers, to work together to deliver to production, successfully and smoothly, an application and its database.The purpose of change management is to protect the integrity of the database design throughout the development process, to identify what changes have been made, when, and by whom and, where necessary, undo individual modifications.
Regardless of the specific development methodology employed (ITIL, Scrum etc.), it is vital that a process is put in place to manage all these people, their code and the environments.In support of this process, tools will be needed in order to automate builds and deployments because, with this many people and this many environments, attempting to deploy manually would be a time-consuming, error-prone exercise in frustration.The goal of the process is to enable large teams of developers to work on the same project, at the same time, without stepping on each other’s toes. It may be vital financial information or it may be very simple lookup data that helps you maintain consistency.If all this isn’t enough, the very purpose of having a database, keeping data, storing it, retrieving it, presenting it to the user, means that you can’t just throw away yesterday’s database. Regardless, it needs to be kept around and that makes the job of building databases even harder.You have to be able to retain data even as you make changes to the underlying structure.