Download presentation
Presentation is loading. Please wait.
1
Database version control
Konstantin Proskurdin
2
Models of work with database
One database per project One database per developer One database per team
3
One database per project
4
One database per project
Advantages Easy to sync changes Disadvantages Change of one developer could stop work of whole team
5
One database per developer
6
One database per developer
Advantages Independent development Disadvantages Sync of databases is required
7
One database per team
8
One database per team Advantages Easy to sync changes inside team
Disadvantages Sync of databases is required
9
Why database VSC Track changes history
Possibility to restore database state for hotfixes/feature branches Some kind of backup Continuous Integration and Continuous Delivery
10
Database version control methods
Merge tools Update scripts Migrators SQL Version Control SSDT
11
Merge tools Red Gate SQL Compare ( DevArt Schema Compare ( SQLaccessories SQL Examiner (
12
Merge tools Demo
13
Update scripts
14
Migrators Migrator.NET ( Ecm7migrator ( FluentMigrator ( Entity Framework Migrations ( Flyway (
15
Migrators Demo
16
SQL Version Control SQL Source Control (
17
SQL Version Control Demo
18
SSDT SQL Server Data Tools ( 03/29/sql-server-data-tools-ssdt.aspx)
19
SSDT Demo
20
Database version on CI
21
Database version on CI Merge tools - manual
Update scripts – custom command file Migrators – migrate.exe SQL Version Control – TeamCity plugin SSDT – MSBuild target
22
That’s all
Similar presentations
© 2025 SlidePlayer.com. Inc.
All rights reserved.