I have a project for which we need to create a simple branching strategy to enable the development of new functions, while maintaining bug fixes in another branch.
I have a problem with databases.
The database schema is part of TFS as a database project, but in order to have enough test data that we made at some point, back up the live database and use it for testing during development.
Currently, databases (a common tree) are hosted on a workgroup server with one set of databases for each developer, and each set of databases is updated once a quarter using sql scripts created by other developers when the schema changes.
My question is: How can we reorganize this so that each branch is autonomous, and we can easily switch from one branch to another. I already looked at using SQL Express and placing databases inside a branch, but that didn't work. We also studied creating scripts with all the data and rebuilding the database from the database, but it took too much time, and some developers, as a rule, did not forget to do this often enough.
Any ideas?
source
share