What a P2T actually copies

Production to test copies DATA AND CONFIGURATION, overwriting whatever the target held. Both halves of that sentence surprise people, and the second one is expensive. THE THINGS PEOPLE ASSUME SURVIVE AND DO NOT. Configuration built in test since the last refresh — gone, replaced by production's. Role assignments made in test — gone; the target now has production's users and grants. Sandboxes that were open — gone. Test data somebody spent a week creating — gone, because the target's data is replaced by production's. "A REFRESH" SOUNDS LIKE AN UPDATE AND IT IS A REPLACEMENT. The word does more damage than the operation: people hear it as "bring the data up to date" and it is "overwrite this environment with a copy of another one". Say the second sentence when you are asked to schedule one. What the target GAINS is the other half, and it is Lesson 4 and…

In this module: Module 16 · Environment management: P2T, refreshes and what breaks

1. 1The environments, and what each is for
2. 2What a P2T actually copies
3. 3The checklist before anybody clicksFree preview
4. 4Data masking and why it is not optional
5. 5Preserving configuration across a refresh
6. 6Integrations after a refresh
7. 7Scheduling refreshes around a project
8. 8What breaks: four refresh failures
9. 9Lab briefing · Plan a refresh you could defend