DZone
Database Zone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Over 2 million developers have joined DZone.
Log In / Join
  • Refcardz
  • Trend Reports
  • Webinars
  • Zones
  • |
    • Agile
    • AI
    • Big Data
    • Cloud
    • Database
    • DevOps
    • Integration
    • IoT
    • Java
    • Microservices
    • Open Source
    • Performance
    • Security
    • Web Dev
DZone > Database Zone > 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.

Yaniv Yehuda user avatar by
Yaniv Yehuda
·
Apr. 12, 16 · Database Zone · Opinion
Like (1)
Save
Tweet
4.38K Views

Join the DZone community and get the full member experience.

Join For Free

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:

  • All database changes must be documented, with an enforced system that prevents any change if it isn’t documented (check-out/check-in on the database objects)
  • Another security mechanism on top of Oracle/MS-SQL that integrates with the company Active Directory, and can control who performs check-out/check-in
  • A system to generate the database deployment script from the source control repository. This system should utilize the baseline aware analysis to raise any red-flags and aid in conflicts merging
  • 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".

    Production (computer science) Database

    Published at DZone with permission of Yaniv Yehuda, DZone MVB. See the original article here.

    Opinions expressed by DZone contributors are their own.

    Popular on DZone

    • CockroachDB and Deno: Combining Two “Quick to Start” Technologies
    • Deriving Ideal Indexes: A Guide
    • Key Highlights from the New NIST SSDF
    • The Differences You Should Know About Java and Python

    Comments

    Database Partner Resources

    X

    ABOUT US

    • About DZone
    • Send feedback
    • Careers
    • Sitemap

    ADVERTISE

    • Advertise with DZone

    CONTRIBUTE ON DZONE

    • Article Submission Guidelines
    • MVB Program
    • Become a Contributor
    • Visit the Writers' Zone

    LEGAL

    • Terms of Service
    • Privacy Policy

    CONTACT US

    • 600 Park Offices Drive
    • Suite 300
    • Durham, NC 27709
    • support@dzone.com
    • +1 (919) 678-0300

    Let's be friends:

    DZone.com is powered by 

    AnswerHub logo