Enterprises with digital aspirations now realize it’s DevOps or die. The increase in agility gained from short, automated deployment cycles is staggering, and it’s a matter of when, not if, software engineering teams make the switch. The problem is that, although enterprises spend a lot of time and effort on a DevOps transformation, they often leave database development processes outside of the DevOps and DevSecOps loops.

1. 3 secrets to help you
modernize your database
environment

2. 2
Presenters
Yaniv Yehuda
Yaniv Yehuda, co-founder and CTO at DBmaestro
Scott Willson
ARA Product Marketing Director at CA-Automic Software

3. 3
Agenda
3 secrets to help you modernize your database environment
• Latest insights and observations from CA-World; DevOps Enterprise Summit;
DBmaestro 2018 Database DevOps Survey
• How winning organizations are bringing the database back into their DevOps
culture
• How to ensure the right balance between developer liberty/capability,
DevSecOps controls, and database control
• How to extend the best practices gained through sweat, blood, and tears in
your DevOps environment to the database

4. 4
Insights & Observations

5. 5“Enterprise DevOps Adoption Isn’t Mandatory— but Neither Is Survival.”
– Gene Kim, The Wall Street Journal, CIO Journal, May 22nd, 2014

6. 6
DevOps or Die!
Percent of IT projects using DevOps approach
Source: DBmaestro 2018 Database DevOps Survey

7. 7
Did you forget anything?
Figure 4: Continuous Delivery Adoption Rates
None
20%
To some
extent
41%
Mostly
23%
Fully
16%
Figure 3: Integration of DBAs
with DevOps Teams
Source: DBmaestro 2018 Database DevOps SurveySource: DBmaestro 2018 Database DevOps SurveyNo interest Fully

8. 8
• Danger of homogeneous groups
• Group polarization
• “nonpolarized groups consistently make better decisions
and come up with better answers than most of their
members, and surprisingly often the group outperforms
even its best member.”
• Surowiecki, James (2005-08-16).
• The Wisdom of Crowds (pp. 188-189).
• Knopf Doubleday Publishing Group. Kindle Edition.
The Need For Dev + Ops, A Study in Group Thinking

9. 9
Secret #1
Source: DBmaestro 2018 Database DevOps Survey
Figure 11: Top 3 Reasons For Errors When
Making Changes to The Database

10. 10
Database Source Control
Integrated Source Control ProcessDevelopment Process
• Check in & out
• Labels
• Change History
• Conflict identification& Merges

11. 11
Database Source Control
Results:
• 15% productivity gain
• Significant reduction in
re-work
• No more accidental
code-overrides
• Complete history of
changes
• Eliminate partial
deployments
Revision history
Actions
Standard IDE
Change
Management

12. Who should introduce changes to
you database and how?
Secret #2

13. 13
The old days: waterfall... safe but slow
The Dev team is responsible for:
• Creating logical changes to the app/DB
The DBA is responsible for:
• DB changes code reviews (especially
around high risk areas)
• Handling rollout and rollout risks
• The health and continuous operation of
the DB
The Problem? Slow process…

14. 14
Modern days – going faster
Agile : small focused
• Every 2-3-4 weeks?
• Continuously?
CI /CD
• Small/atomic changes
• Quick feedback loops (unit tests, automated
tests…)
• Small changes being quickly pushed all the
way to (pre) production
Who is responsible for rollout risks? Blamestorming is inevitable…

15. 15
Secret #2
15
Source: DBmaestro 2018 Database DevOps Survey
Figure 15: Access to Make Database Changes
14%
29%
37%
8%
10%
3%
24%
38%
23%
6% 6% 4%
More than
once a day
More than
once/week
A couple of
times/month
Once/month A few
times/quarter
A few
times/year
2017 2018
Figure 7: Frequency of Application Deployments by DevOps

16. 16
Policies, Permissions & Compliance
• Security roles: control who can do what and where
• Policy: what can be done, where and when
• Audit: who did what, when and why

17. 17
Secret #3
17
Figure 16: How Database Changes Are PerformedFrequency of DB changes vs. last DB crash
Source: DBmaestro 2018 Database DevOps SurveySource: DBmaestro 2018 Database DevOps Survey
Execute scripts
51%
Build / submit
scripts with
automation tool
34%
Execute SQL
commands
15%

18. 18
Database Release Automation
• Comply to policy rules
• Enforce security roles
• Prevent non-policy updates
• Validate pre-release configuration
• Stop automation
• Notify Drift
• Suggest resolution
• Execute upgrade
• Audit changes
• Validate post-release results
• Activate tests
• Enable rollback if required
• Alert or prevent out of process changes
Validate
Validate
‘Break Glass’
Out of Process Change
Automate the proven
waterfall process
QA Staging Prod.SQL
Script

19. 19
Release Pipelines -Fast, Safe, Repeatable, Scalable

20. 20
Automatic Database Drift Detection

21. 21
Scorecards – measure, so you can improve…

22. 22
Following Proven Industry Practices!
Effective &
productive
Safe, predictable,
scalable & controlled
Sec
Dev Ops
Check in
& out,
Change
History
Binary
Repository
Labels,
Conflict
identification
& Merges
Roles,
Permissions
Policies &
Audit
Git / SVN /
Perforce…
ARA (Jenkins,
CA-Automic
and others) Configuration
validation,
Roles, Policies,
Auditing,
Rollbacks
Dashboards,
Scorecards

23. 23
Enterprise Scale
Dev Sec
Ops
100% Secure,
Control, Audit
10X Faster time
to market
15% boost
in developer and
DBA productivity
Summary

24. 24
About us
DBMaestro introduces DevOps and automation best practices
to databases for the enterprise, dramatically simplifying,
accelerating, and improving release processes, while
modernizing database development via pipelines long enjoyed
elsewhere in the industry.
Simplifying and automating database deployment processes in an agile
environment while reducing critical application downtime!

25. 25
Next Steps:
• Register to a live demo webinar of DBmaestro’s DevOps Suite
• Wednesday, December 6, 2017, 11:00 AM EST, 4:00 PM GMT
• Download the slides from today’s presentation
• Listen to the recording
• Download the full survey
• CA|Automic Continuous Delivery Map
• Download CA|Automic Action Pack for DBmaestro

26. Thank You!