With the growing popularity of Agile, CI, CD, and DevOps, there must be control within all environments in order for them to succeed. If someone compiles an executable binary in his local environment and copies it to any other environment, the next build and deploy will override his change and all the work he has done will be gone. Today, I hope that no developer would think to copy an executable binary compiled locally to the integration, QA, or production environments.
So, how do we help a DBA keep their access to production?
The new process requires the ability to enforce a separation between the DBA who develops the change, and the DBA who actually executes it. In order to ensure such separation, the following must occur:
To learn more about the right way to implement source control in the database, read our white paper, "The Definitive Guide to Database Version Control".