Quick question, we (in R12) currently load data into dev at month end then promote to stage, then to prod.

So to avoid getting in the way of things we take a branch off dev to do config work, then merge.

This means stage is pretty much unused, we do the data validation in dev before promoting.

Previously, at different place we had the setup to load data to stage and promote it prod or refresh to dev.

This is the traditional software development setup and lets users load test data and mess around with database then get fresh copy, while keeping staging as the full dress rehearsal space for checking new code is good with prod (copy) data and new data works with prod (copy) code before pushing to either Prod.

Not sure if the data to stage then dev is still even option in R12 ... anyone doing it that way?

Or all dev to stage? In which case what do you do with stage?

Thanks

T

Thodi,

In the R11 days we did load data into Staging and then promote the data project to Dev.  However, with the change in R12 to load data into Dev this has allow the system to pre-calculate up to Staging where IT Owners could do a validation before a final promotion to Production.  The benefit of the new setup is that we do not have to wait for the calculation from Staging to Production.  In R11 we had to wait for the environment to be pre-calculated before it was available.  In R12 we do not have to wait for that as the Staging environment is an additional validation checkpoint before going to production and pre-calculated in the background.

Cheers,

Ryan

Just as @Ryan Paul mentioned, R12 is different than R11. I am getting used to loading data in DEV and then check-in to promote to stage. Gone are the days to load data in Stage first. Like you said, we create branch(es) to do any configuration changes and then merge them back to trunk.

In R11, we load into Stage.  In R12 we load into Dev.