From the Blogosphere
The Advantages of a Model-Based Approach
A Safer, Faster, and More Transparent Method of Managing Schema
By: Pete Pickerill
Oct. 31, 2013 02:00 PM
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 a massive collection of individual parts applied in an order you can’t reproduce.
Assessing the compatibility of the schema you develop against in relation to what’s in production is a time consuming and error prone process. When you craft new changes, ferreting out the possible impact on other objects in your schema is not intuitive. The specific business needs associated with the individual parts of your schema get murky over time and it’s harder for you to design to your future instead of accommodating your past. There is no traceable history of who did what and why from environment to environment. Application issues caused by database errors become hard to troubleshoot because there is no easily digestible standard to use as measuring stick in evaluating a malfunctioning environment.
At Datical, we talk a lot about the model-based approach we take to database schema management and how it’s superior to the scenario described above. When you use Datical DB to employ a model of your database schema, everyone in your organization is working with a transparent and comprehensive representation of your entire schema. There’s no more wandering off into the weeds of individual changes with no sense of history or relationship when trying to make sense of your schema. The model enables a faster, safer, and more transparent method of managing your schema. Here are some of the perks:
No need for SQL
Reliable change design based on what your database is, not what you think it should be.
Forecast: Impact Assessment on a Representative Model
Traceable History of the Evolution of your Schema
Easy Comparison of Models
Clear View of Completeness
Latest Cloud Developer Stories
Subscribe to the World's Most Powerful Newsletters
Subscribe to Our Rss Feeds & Get Your SYS-CON News Live!
SYS-CON Featured Whitepapers
Most Read This Week