Best way to load db schema for various releases?
kraades
Posts: 9
We have different releases of the product each with a different database schema.
We would like to load the db schema for all branches into SSC.
DEV (latest db schema V2.1)
-->
MAIN
-->
RELEASE
- V1.0 (db schema V1.0)
- V1.1 (db schema V1.1)
- V2.0 (db schema V2.0)
Etc.
What is the best way/order to load the database schema for REL V1.0, REL V1.1, REL V2.0, MAIN and DEV?
We would like to load the db schema for all branches into SSC.
DEV (latest db schema V2.1)
-->
MAIN
-->
RELEASE
- V1.0 (db schema V1.0)
- V1.1 (db schema V1.1)
- V2.0 (db schema V2.0)
Etc.
What is the best way/order to load the database schema for REL V1.0, REL V1.1, REL V2.0, MAIN and DEV?
Comments
One way would be: when you reach a cutoff point (say, v1.9 is done with, and you're about to start work on 1.10) you could link your DB to a new 1.9 folder in SVN/TFS etc, commit the entire thing, then unlink. This way, you have a separate copy.
It's more normal to just keep working in the same repo though, having made sure the final commit for 1.9 was appropriately labelled. You can then, at any point, update a DB to that version using SQL Compare. Note that this method relies on being able to browse the history revisions though so it won't currently work with GIT/Mercurial etc, you'd need to be on SVN/TFS.
Redgate Software