Since there will be a lot of database editing, there is a need to automate the process of putting the db changes under git.
e.g. creating a script that will use MSSQL's exporter to dump all the database as alter scripts including content. More details regarding this can be found here.
The process should be relatively easy and will allow to track each table changes in a separate file, so new users don't need to restore a .bak file, rather run a script that will import the database from the generated script.
Since there will be a lot of database editing, there is a need to automate the process of putting the db changes under git.
e.g. creating a script that will use MSSQL's exporter to dump all the database as alter scripts including content. More details regarding this can be found here.
The process should be relatively easy and will allow to track each table changes in a separate file, so new users don't need to restore a .bak file, rather run a script that will import the database from the generated script.