Closed Bug 1082020 Opened 9 years ago Closed 9 years ago

Port production database to Dev and Stage


(Websites ::, defect)

Not set


(Not tracked)



(Reporter: ckoehler, Unassigned)


(Whiteboard: [kanban:] [dev=2014-10-23] [stage=2014-10-23])

Please update dev and stage database from production. Thanks!
Whiteboard: [dev=2014-10-16]
Whiteboard: [kanban:]
Whiteboard: [kanban:] → [kanban:] [dev=2014-10-23] [stage=2014-10-30]
Depending on how long it takes to do this, we might want to set a timeline for how often it's done.

Assuming it's not something that can be done to both environments every week, these are my thoughts:
* If there is an asymmetric lag, stage should be closer to prod than dev is.
* Stage should be synced no less than once per month.
* Dev should be synced no less than once per quarter.
Because we do so much initial testing on dev, I actually prefer that be updated monthly if possible.
JD updated the dev and stage databases from production.  The process takes approximately 30 minutes per environment.  I don't know if there is old spam in the wiki database that needs to be cleaned out, which might reduce the size of the database.

I don't know if its feasible to earmark one of the wiki release sessions per month for doing the database update.  In discussions w/ JD, it also sounded like it might be useful to occasionally optimize the production wiki database to clean up any fragmentation.
Closed: 9 years ago
Resolution: --- → FIXED
30 minutes per environment is a lot and you're right in that it probably doesn't make sense to use up an entire release cycle just for this. 

I'll file another bug for figuring how how to handle db migrations etc.
Whiteboard: [kanban:] [dev=2014-10-23] [stage=2014-10-30] → [kanban:] [dev=2014-10-23] [stage=2014-10-23]
You need to log in before you can comment on or make changes to this bug.