Configuration management for database short overview
Upcoming SlideShare
Loading in...5
×
 

Like this? Share it with your network

Share

Configuration management for database short overview

on

  • 606 views

The document describes author's strategy and their successful implementation of a configuration management for a database project. The document is meant for professionals who have similar experiences ...

The document describes author's strategy and their successful implementation of a configuration management for a database project. The document is meant for professionals who have similar experiences and it doesn’t assume any specialized technical backgrounds. It might help project managers or config managers to compare and choose the best solutions for their organizations.

Statistics

Views

Total Views
606
Views on SlideShare
606
Embed Views
0

Actions

Likes
0
Downloads
18
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Configuration management for database short overview Document Transcript

  • 1. Configuration Management for Databases Short Overview Robert Berliński, support Mercedes Gavilan Document version 0.3, 2 February 2012PrefaceThe document describes authors strategy and their successful implementation of aconfiguration management for a database project. The document is meant for professionals whohave similar experiences and it doesn’t assume any specialized technical backgrounds. It mighthelp project managers or config managers to compare and choose the best solutions for theirorganizations.IntroductionIT configuration management process is a complex system. There are two basic ways fordelivering changes. One way is to build an entire solution that includes both modified andunmodified components (an example is an EAR file for a web application). The other way is tocollect and deliver only the differences that update a system from version A to version B (anexample is updating a database).Unfortunately organizing components that define difference for a database is not that simpledue to the technical characteristic of a database. Configuration management procedures need toconsider not only code changes but all relations between model changes and data. The relevantchanges need to be managed together and in the correct order. It means that a configurationmanagement process should preserve the order of changes and deliver them to a database in thesame order.On the top of that, the procedure should be as flexible as possible and it shouldnt absorb toomuch time either.The solutionThe first mail stone is to place a versioning repository using trunk and branches in the center ofconfiguration management for databases. It is the same concept as with Java projects butextended to address the issues typical for a database. It will allow simultaneous development indedicated branches and control of changes made to a database.Copyright © www.scmsupport.com 2012. All Rights reserved. Page 1/3
  • 2. Illustration 1 - the specific directory structure in version repository.The second mailstone is to automate the process of building patches/upgrades that deliverchanges and make them in a form of runable scripts for the administrators convenience.Illustration 2 - the generic strategy.The patches building tool follows rules that allow to recognized all changes and deliver bothsource objects and scripts preserving the correct order and dependencies.Copyright © www.scmsupport.com 2012. All Rights reserved. Page 2/3
  • 3. Illustration 3 - the process of delivering changes.SummaryThe solution delivers important benefits that can be transferred to configuration managementfor another database projects: Provides control over the code changes and makes possible to answer the questions who, when and for what reason changed what part of a code. Allows teamwork and concurrent projects, giving project managers more flexibility in scheduling changes considering limited resources. Automates most of the processes of delivering changes, it saves config managers and administrators time as well as eliminates many areas for human mistakes. Can serve as the base for automated tests and for continues integration.If you would like to learn more, please visit www.scmsupport.com. There are references todocuments that describe in more details the procedures and the technicalities. Thank you foryour attention.Copyright © www.scmsupport.com 2012. All Rights reserved. Page 3/3