Timeline for Move data chunk from table with 200+million rows to a new table MySQL
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 28, 2017 at 19:12 | history | edited | Rick James | CC BY-SA 3.0 |
archiving
|
| Apr 28, 2017 at 19:05 | comment | added | Rick James | What do you do when there is a power failure? Network failure? Lose data? Stall the clients of the API? Another tack... Do you have Replication setup on RDS? | |
| Apr 24, 2017 at 5:57 | comment | added | Asad M | Since the data is constantly coming through API calls, how do you suggest to stop the writes? If a there's a way, we can stop for minutes but not hours. By the way this activity is more of data archiving which will happen more often so you can suggest some other solution too. | |
| Apr 22, 2017 at 18:20 | history | answered | Rick James | CC BY-SA 3.0 |