1. Database version control
Konstantin Proskurdin

2. Sponsors

3. Models of work with database
One database per project
One database per developer
One database per team

4. One database per project

5. One database per project
Advantages
Easy to sync changes
Disadvantages
Change of one developer could stop work of whole team

6. One database per developer

7. One database per developer
Advantages
Independent development
Disadvantages
Sync of databases is required

8. One database per team

9. One database per team Advantages Easy to sync changes inside team
Disadvantages
Sync of databases is required

10. Why database VSC Track changes history
Possibility to restore database state for hotfixes/feature branches
Some kind of backup
Continuous Integration and Continuous Delivery

11. Database version control methods
Merge tools
Update scripts
Migrators
SQL Version Control
SSDT

12. Merge tools
Red Gate SQL Compare (
DevArt Schema Compare (
SQLaccessories SQL Examiner (

13. Merge tools Demo

14. Update scripts

15. Migrators
Migrator.NET (
Ecm7migrator (
FluentMigrator (
Entity Framework Migrations (
Flyway (

16. Migrators Demo

17. SQL Version Control
SQL Source Control (
Source control for SQL Server (
dbForge Studio for SQL Server (

18. SQL Version Control Demo

19. SSDT
SQL Server Data Tools (

20. SSDT Demo

21. Database version on CI

22. Database version on CI Merge tools - manual
Update scripts – custom command file
Migrators – migrate.exe
SQL Version Control – TeamCity plugin
SSDT – MSBuild target

23. That’s all