Dcm for ilOUG

CONTROL.DEPLOY.PROTECT.COMPLY

DCM & SCM

ilOUG .NET forum
2012

Footer www.dbmaestro.com

DCM
 DCM – Database Change Management
 Part of ALM (Application Lifecycle Management)
solutions

Footer www.dbmaestro.com 2

Applications & Databases
 Database is a Major Part of the Application
 Schema Structure
 PL/SQL Code
 Lookup Content
 Database is a
Central Resource
 Business Data Must
be Saved


SCM Concepts
 Structure of a repository & gained functionality
 File based
 Separation of Working
environment and repository
 File Locking
 Check out / in
 Baseline
 Tag / Label
 Head / Latest
 Rollback
 Compare / Merge
 Deploy / Build

SCM Concepts did not apply to
the database world
 Traditional SCM concept doesn’t fit the Database
world…
 A database is not a collection of files
 DDL (Data Definition Language)
 DML (Data Manipulation Language)
 DDL extraction
 No debug environment
 Content ?
 Database duplication – constant synchronization


SCM Concepts did not apply to
the database world
 Moving changes…
 Development to QA, integration and production
 Code – simple file copy & registration
 DB objects cant just be “moved” – content…
 What do we do with db content changes ?

 So the whole thing was neglected for years...

 Manual process where created to deal with
eal life situations


Manual process
 Lists depicting database changes are created
Post-it
SCM
Don’t forget to
add the index…

 Detailed documents in SCM

 Code is written to alter database
structure without content loss


Manual process
 But:
 Lists are usually not part of an SCM process
 Not mandatory
 Not policy enforced
 Code developed for deployment is not part of ALM
 Not following the same restrictions
(QA, code review…)
 No simple solution for content change management
(backups? Database duplications?)

 Clearly, automation is required!

Automation – First Generation database
change management
 A new concept is created
 Compare & Sync
 Automated tools compare different environments
 Reports are generated, and differences are found
 Automatic code generation
 Some products can even analyze content and propagate
content changes
 Deployment became more stable and less
prone to human mistakes

 We where happy for a while…

change management
 But:
 What if test environment has undergone changes?
 What happened while in development cycle?
 Anyone privileged can update the database, even if it is
not required…
 How can we match database development with
application development?
 Partial deployments?
 Team synchronization?
 Who did What, When and Why?
 So, a lot of the traditional SCM goals are not answered
 Footer www.dbmaestro.com 10

change management
  File Locking
  Check out / in
  Baseline *
  Tag / Label
  Head / Latest, but this it the DB itself, so actually  …
  Rollback
  Compare /  Merge
  Deploy / Build *
* Partial


SCM without DCM
Business Req. Conflict code Automated Continuous
SCM Native Code
Integration Resolver Deployment Integration

File Based Change Merge Agile Any Change
Version Management Code Tested Over
Control: Systems Quick Night
Java, .NET, Iterations
C#, C++ Correlate
Change with Reduce
Activity Overhead

Increase
Team
Satisfaction


DCM Lack of Inherent Risks
 Falling Behind Deadlines
 Code Overrides
 No Tracking Changes
 Release Rollback
 Lack of Recovery
 Release Unreliability
 Lack of Automation
 Audit Compliance
 Security Breaches


Correction

This is not
Database Change Management
This is
Database Deployment Management
So,
We still need to
Manage Change

Next generation
database change management
Requirements
 Follow traditional SCM concepts
 Check-Out / Check-In / Tagging / …
 Support Any Database client IDE

 Enforce a well disciplined change process
(no out of process updates)
 Synchronize team work
 Support entire life cycle
(development, testing, going to production)


Next generation
database change management
Requirements
 Manage content changes
 Good, stable repository
 Save all development
 Auditing

 Link / embed to traditional SCM projects
 Enable deployment based on SCM tasks


Follow SCM Concepts
NG database change management
Requirements
  File Locking
  Check out / in
  Baseline
  Tag / Label
  Head / Latest
  Rollback
  Compare /  Merge
  Deploy / Build

Without DCM
Two unrelated Processes

Compile Script
Check-Out in DB
Script

Check-In Script Modify Script

Debug Script
Get updated in DB
Script from DB


With DCM
One Enforced Process
Check-Out
Object

Modify Object in
Check-In Object
DB

Run Applications’
Tests


NG database change management
How is it done?
 Challenges:
 Creating a new type of repository
 A problem - central resource vs. replicated resource
Enforcing change process


Synchronizing development teams


 Linking to traditional SCM
Linking versions


Linking change sets


 Leveraging deployments

Benefits & Risk Avoidance
 Policy enforcement
 Concurrent development
 Preventing collisions and conflicts

 Standards
 Check-in and check-out
 Labels

 Complete audit trail of all changes


Benefits & Risk Avoidance
 Lookup tables data management

 Automated Roll back of changes
 Development
 Production systems

 Automated deployments between multiple databases
 Three way analysis
 Requirement based deployment


It’s all about a Safety Net
DCM Business
Conflict code Automated Continuous
SCM Native Code Database Req.
Resolver Deployment Integration
Code Integration
File Based Database Change Merge Agile Any Change
Version Version Management Code Tested Over
Control: Control Systems Night
Quick
Java, .NET,
Iterations
C#, C++
Change Correlate
Policy Change with
Reduce
Activity
Overhead
Automatic
Deployment
Increase
Script
Team
Satisfaction


Demo


Baseline in Deployments

Source vs. Action Source vs. Target vs. Action
Target Baseline Baseline

= No Action = = No Action

≠ = Override
≠ ? =
≠
≠
≠
Ignore
Merge

You do not have all With Baseline the
the information unknown
is now known


DCM & Development Methodologies
 Agile
 Branches
 Multiple Development – short & long development
 Shared Environment
 Teams’ Environment
 Design tools
 ORM tools


Summary
 SCM works well with File-Based objects
 DCM created for Databases objects

 Support ALL IDEs working with the Database
 Support ANY development methodology

 Prepare yourself to the deployment phase


Thank you

Thank you for your time

Uri Margalit
urim@dbMaestro.com

Dcm for ilOUG

Recomendados

Recomendados

Mais conteúdo relacionado

Mais procurados

Mais procurados (18)

Destaque

Destaque (7)

Semelhante a Dcm for ilOUG

Semelhante a Dcm for ilOUG (20)

Último

Último (20)

Dcm for ilOUG