Join us to see Redgate's latest database DevOps innovations, which empower developers to code in the IDEs of their choice, version control database changes in plain SQL, and easily validate their changes against a masked copy of production as soon as they make the change. By integrating cloning technology into proven developer workflows, Redgate: • Provides a platform for easy and safe experimentation and innovation • Reduces time to market for changes by removing manual work and enabling Continuous Delivery • Supports continuous quality with static code analysis and automated testing functionality Kendra Little will show you Redgate's recent innovations in action and give you a picture of where Database DevOps is going, and why.

1. The Future of DevOps
Fully Left-Shifted Deployments with Version
Control and Automatic Cloning

2. Agenda

3. What’s So
Hard About
Database
DevOps?

4. Databases
didn’t start as
code

5. Warring
factions
across silos

6. Split
approaches to
version
control

7. Solution 1:
Early
feedback &
response

8. Clone as baseline
A baseline clone represents
the production database at the
time development begins
Individual migration scripts
applied to clone to simulate
production deployment

9. Another view
No code
validation, created
in seconds
regardless of
complexity
ALTER TABLE A
ADD COLUMN B
INT NOT NULL
… UPDATE A set B =
‘val’ where lastmod
> ‘criteria’
…. ALTER TABLE
A modify B NOT
NULL
CREATE
FUNCTION
…
A baseline clone represents
the production database at the
time development begins
Individual migration scripts
applied to clone to simulate
production deployment

10. Why this model changes the game
Fully left-
shifted
production
deployments
Quick rollout of
Database
DevOps
across an
Enterprise
Fast build
performance
even for
complex
databases
Start where
you are – even
with invalid
code or
circular
references
Simple re-
baselining

11. Who are the vanguards?
• Code quality is critical
• Legacy databases
• Enterprises who want
many teams using the
same workflow, fast
• Frequent releasers
• Complex logic in the
database
#1. Financial
Services
#2. Healthcare
#3. IT/Tech

12. Solution 2:
Branch
Alignment

13. • Isolate your work
• Be able to share your
work safely
• Git encourages
branching workflows
to manage conflicts
Why use branches in Git?
https://www.red-gate.com/blog/the-managers-guide-to-git-
training-for-database-administrators

14. • Implemented via GitHook
• Creates a new clone every
time you check out a
branch
• Renames clones for other
branches for fast switching
Automatic cloning for Git Branches
https://www.red-gate.com/hub/product-learning/sql-
clone/how-sql-clone-and-sql-change-automation-enable-
seamless-database-branch-switching

15. Demo

16. The “New
Normal” of
Database
DevOps

17. The “New Normal”
Code in IDEs of choice
Version control database changes in plain SQL with static code analysis
Fully left-shifted production deployment validation with automated drift
detection
Fast rollout of Database DevOps across an Enterprise, no matter the
complexity of the database or quality of the code
Fast, scriptable setup of development, test, and QA environments with
minimal storage footprint

18. Learn more

19. Technical Articles
• SQL Change Automation:
Adding SQL Clone to the Mix
• Getting Started with
Automatic Database Branch
Switching
Research
• State of Database DevOps
• Accelerate State of DevOps
Workflows and Guidance
• How to Enable Fast Database
DevOps Adoption Across
the Enterprise
• Key Patterns for Database
DevOps in Financial Services
• Problems and Solutions for
Agility with Legacy Monolith
Databases
Content to share