Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

2 DBs having schemas that represent the same semantic objects. The first one is production DB (Non-RDBMS, in-house implemented in-memory DB with shitload of RAM). Other is Postgres.

Once in a while the production DB is changed (schema upgrade).

Question: what is the best practice to keep DBs of different types aligned semantically?

share|improve this question

closed as not a real question by dezso, StanleyJohns, Mat, Mark Storey-Smith, Max Vernon Jun 24 '13 at 1:32

It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center.If this question can be reworded to fit the rules in the help center, please edit the question.

Possible duplicate from SO:… – Bacon Bits Feb 21 '13 at 19:45
Keep in mind that your options are going to be severely limited if you're using a custom, in-house database. Additionally, it's generally considered best practice for dev and prod to at least use the same systems. Having dev be Postgres but prod be custom-memory.db is a little awkward. – Bacon Bits Feb 21 '13 at 19:47
We are quite satisfied using Liquibase for this. – a_horse_with_no_name May 23 '13 at 8:33

keep all SQL DDL in "patch" files in source control.

add a "schema_version" table to your database and track the latest patch file you are on.

write a script that runs new patches against your dbs.

share|improve this answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.