How DBAs Can Keep Access To Production
How DBAs Can Keep Access To Production
DBAs really need to have access to production environments, Yaniv Yehuda explains one way of doing this.
Join the DZone community and get the full member experience.
Join For FreeRavenDB vs MongoDB: Which is Better? This White Paper compares the two leading NoSQL Document Databases on 9 features to find out which is the best solution for your next project.
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".
Get comfortable using NoSQL in a free, self-directed learning course provided by RavenDB. Learn to create fully-functional real-world programs on NoSQL Databases. Register today.
Like This Article? Read More From DZone
Published at DZone with permission of Yaniv Yehuda , DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.
{{ parent.title || parent.header.title}}
{{ parent.tldr }}
{{ parent.linkDescription }}
{{ parent.urlSource.name }}