Welcome!

The DevOps Database

Pete Pickerill

Subscribe to Pete Pickerill: eMailAlertsEmail Alerts
Get Pete Pickerill via: homepageHomepage mobileMobile rssRSS facebookFacebook twitterTwitter linkedinLinkedIn


Top Stories by Pete Pickerill

Recently, the Agile Austin DevOps SIG invited Datical to talk about the impact of DevOps practices on database change management. This was a great opportunity for us to talk to folks about our approach to managing application schema change in IT organizations that have moved or are moving to more responsive and agile planning, development, and delivery processes.  It was a lively discussion with some great feedback from the audience. In framing the discussion, I relied heavily on "The Three Ways" of DevOps.  The Three Ways are the principles that underpin the DevOps patterns that Gene Kim discusses in detail in his novel "The Phoenix Project" and in the"The DevOps Cookbook", written by John Allspaw, Patrick Debois, Damon Ewards, Jez Humble, Kim, Mike Orzen, & John Willis.  Here's a quick summary of The Three Ways: The First Way: Systems Thinking - This Way stresses... (more)

SMG Research Reveals DBA Tools Not Effective for Managing Database Change

New research from Simon Management Group reveals that despite the high percentage of companies who use DBA tools, a majority of companies still struggle with database change and configuration management issues that impede the first-time success rate of business-critical application deployments. Commissioned by Datical, Inc., the study examines the views of application development and deployment professionals in large organizations with $100 million or greater in IT department spending. The companies surveyed have similar characteristics including a large number of applications in ... (more)

The Advantages of a Model-Based Approach

The vast majority of schema management today is handled through the generation, review, and execution of SQL scripts.  These scripts can be tiny or huge; they can encapsulate the creation and relationships of several objects or they can describe a one-time alteration to a single object.  Once executed they generally leave no history of their passing other than the presence of the pieces they create, delete or modify; you can be dependent on hundreds of small scripts or on one giant script to build out new environments or evaluate existing ones.  You’re left with a schema that is ... (more)

The DevOps Database | Part 4

In the final post in this series about bringing DevOps patterns to database change management, we’re going to discuss the Third Way.  Here’s a refresher on the Third Way from the introductory post in this series: The Third Way: Culture of Continual Experimentation & Learning – This way emphasizes the benefits that can be realized through embracing experimentation, risk-taking, and learning from failure.  By adopting this kind of attitude, experimentation and risk-taking lead to innovation and improvement while embracing failure allows the organization to produce more resilient p... (more)

Don't Forget the Database By @PetePickerill | @DevOpsSummit #DevOps

When you look at the evolution of IT in the enterprise, innovation has really taken hold within the last few years. In the systems and infrastructure part of the stack, virtual machines and the public cloud have greatly reduced the need for server floorspace, cooling and other investments that are overhead-intensive. That's very tangible evidence of innovation. On the application layer of the stack, developer teams have been boosted by DevOps tools and Agile methodologies. The evidence of that innovation manifests itself in dev teams' ability to go faster than ever and constantly... (more)