WARNING: LONG QUESTION.
[Question]
If the strategy is to have a branch on the database, as described below, where the scripts are versioned.
How do you solve data migration issues when trying to consolidate to fewer branches?
Is it just the costs you incur as part of the data transfer?
Essentially, conversion scripts must be created during the migration.
Is there a better way?
Is it possible to solve both problems at the same time?
What is the best practice?
[BACKGROUND]
At my workplace we have a product that has 3 branches. Mainline with the latest LAST AND BIG changes that are not necessarily ready for release.
- Version B (names changed to protect the perpetrators)
- Version A (names changed to protect the perpetrators)
- Highway
Because of these branches, there are 3 versions of the database. Version control of the code is quite simple, but managing the version of the database seems difficult.
After reading, Do you use a source control for your database items? It is best to export all creation scripts for each object / table. NOTE. How you handle this, in one large script or in multiple scripts or hybrids, is your preference according to this article.
I agree with this and asked why this is not done.
.
, , .
.
.
A B , , . , script, , A, B . , , . , , script.
A, A, .
[]
, .