Some of You Will "Git" This

If you could make a "pull request" for production data, how might that look?

Perhaps:

• ✅ A before / after comparison of the values that had changed
• ✅ Security (who can submit / approve in each "repo")
• ✅ Only store the changed data (not full copies)
• ✅ A new "diff" when the base table changes
• ✅ Ability to choose one or more approvers
• ✅ HOOK scripts before / after a commit
• ✅ Tests (DQ checks) prior to merge
• ✅ A pipeline following a merge
• ✅ Emails for "status" changes
• ✅ Comments by reviewers
• ✅ Full history of changes

Sound familiar? This is exactly how developers have managed code for decades - and Data Controller brings the same discipline to data. Every edit to a table in SAS® goes through an edit - stage - approve workflow: changes are staged as a diff, checked by validation rules and hook scripts, reviewed and approved by the people you choose, then loaded. The audit trail captures who changed what, when and why - the git blame of master data.

If you're ready to "commit" to Data Control, we invite you to "clone" the latest version of Data Controller for SAS® - which has ALL these features - and "push" to your "main" environment for some "master" data management!