Timeline for Best practices for schema changes and data migrations to a live database without downtime?
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 17, 2017 at 1:22 | comment | added | Wildcard | @SandeepanNath, to answer question 3 in your comment: because if you (a) bring up new structure, (b) migrate data to it, (c) change your code to write data to the new structure instead of the old, then all data changes made between step b and step c will only exist in the old structure. The question was how to make schema changes without downtime. Read this answer again, carefully. | |
| May 13, 2016 at 18:42 | comment | added | Sandeepan Nath | I have a few questions while trying to understand the scenario for which you proposed this answer - 1. Will the code changes be deployed along with the start of the db changes? 2. Why will there be a need to write to both the structures? 3. Why cannot the new structure be brought up first and then the existing data be migrated and then the code changes be deployed which will populate the new structure? 4. Why is there a need to find out what is not there (your 1st query)? Are you proposing insertion in multiple attempts? | |
| Jan 19, 2012 at 22:10 | vote | accept | Dan Leary | ||
| Jan 18, 2012 at 23:57 | history | answered | Erwin Brandstetter | CC BY-SA 3.0 |