Utility · Database operations
Production to QA and Dev data refresh
A notification table was copied from Production into QA and Dev with no database link between them: a read-only extract, a restorable backup of each target, an uncommitted load and a commit only after the fingerprints matched.
Client names are withheld; details are shared on request.
The problem
QA and Dev had drifted from Production, so tests were no longer realistic. There was no database link between environments, and Production could not be put at risk.
How it was done
Data was read from Production with a read-only extract. Before touching QA or Dev, a restorable backup of each target table was taken. The new rows were loaded without committing, and fingerprints of the loaded data were compared with Production.
Commit only when the numbers match
All four fingerprint checks matched before anything was committed. Two backups were kept so either environment could be rolled back, and Production was never changed.
Tell me about your project
Describe the problem in a few lines. I reply within one business day with questions or a proposal for a free 30-minute call.