Channels ▼
RSS

Tools

Ensuring Database Quality


Scott is a DDJ Senior Contributing Editor and author of numerous IT books. He can be contacted at www.ambysoft.com/ scottAmbler.html.

Last month, I summarized a July 2006 survey exploring the current state of data management within IT organizations. The area of greatest concern revealed by this survey is the abysmal level of database testing: 96 percent of organizations considered data to be a corporate asset and 64 percent implemented mission-critical functionality within the database, yet only 40 percent had tests to validate the data and 46 percent the functionality. Worse yet, the survey revealed a lack of recognition that we need to be doing database testing at all—only 32 percent of organizations not testing for data quality, and 39 percent of organizations not testing database functionality realized that they needed to do so. Clearly something is amiss.

There are three fundamental reasons why you need to develop a comprehensive testing strategy for your RDBMS:

  • First, data is an important corporate asset and you must ensure that its quality is sufficient for your needs.
  • Second, because it is common to implement functionality within a database in the form of stored procedures or stored functions, you must validate this functionality.
  • Third, a regression test suite for your database enables modern evolutionary development practices such as database refactoring. Because all modern software development processes are evolutionary in nature, I believe that data professionals must adopt evolutionary techniques such as regression testing and refactoring.


Related Reading


More Insights






Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

Dr. Dobb's encourages readers to engage in spirited, healthy debate, including taking us to task. However, Dr. Dobb's moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing or spam. Dr. Dobb's further reserves the right to disable the profile of any commenter participating in said activities.

 
Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
 

Video