This is based on my Team Based Development with Version Control talk, which has evolved a bit.
Abstract
Getting your database under version control is ultimately a way of communicating changes and collaborating with team members, maintaining an audit trail and ensuring you always have a version to roll back to.
In this session, we’ll cover why this gives you and your team a crucial advantage in reducing the risk in your development processes. We’ll also discuss another door that your team opens by adopting solid version control: setting up the fundamentals of continuous integration. You will learn what build automation means as a first step towards continuous integration and the value it brings as part of your evolving deployment process. We’ll also discuss branching strategies, and how to manage this for databases as part of your evolving deployment process.
Goals
- Understand the value of version/source control for databases
- Learn the tools, standards, patterns and best practices needed to manage a database from source control
- Identify the necessary flow within a team needed to develop a database with source control
This talk includes the following demos:
- Move database DDL into VCS manually
- Link database DDL and lookup data with SQL Source Control
- Make development changes and check into VCS
- Setup a new developer DB linked to VCS
- Changes flowing back and forth between developers
- Resolving conflicts between development changes made by two people
- Basic branching of code for bug fixes and linking a database for development work to an old branch
Length: 45-75 minutes. Shorter lengths with fewer demos.
Voice of the DBA 