We use cookies and other similar technologies (Cookies) to enhance your experience and to provide you with relevant content and ads. By using our website, you are agreeing to the use of Cookies. You can change your settings at any time. Cookie Policy.


Blog: William McKnight Subscribe to this blog's RSS feed!

William McKnight

Hello and welcome to my blog!

I will periodically be sharing my thoughts and observations on information management here in the blog. I am passionate about the effective creation, management and distribution of information for the benefit of company goals, and I'm thrilled to be a part of my clients' growth plans and connect what the industry provides to those goals. I have played many roles, but the perspective I come from is benefit to the end client. I hope the entries can be of some modest benefit to that goal. Please share your thoughts and input to the topics.

About the author >

William is the president of McKnight Consulting Group, a firm focused on delivering business value and solving business challenges utilizing proven, streamlined approaches in data warehousing, master data management and business intelligence, all with a focus on data quality and scalable architectures. William functions as strategist, information architect and program manager for complex, high-volume, full life-cycle implementations worldwide. William is a Southwest Entrepreneur of the Year finalist, a frequent best-practices judge, has authored hundreds of articles and white papers, and given hundreds of international keynotes and public seminars. His team's implementations from both IT and consultant positions have won Best Practices awards. He is a former IT Vice President of a Fortune company, a former software engineer, and holds an MBA. William is author of the book 90 Days to Success in Consulting. Contact William at wmcknight@mcknightcg.com.

Editor's Note: More articles and resources are available in William's BeyeNETWORK Expert Channel. Be sure to visit today!

Oops, what is that I tripped on? Oh, it’s another new column-oriented data warehouse appliance. If you haven’t noticed, in 2007, Vertica, ParAccel and Calpont have emerged with a column orientation to their DBMS and the appliance model to their delivery. By the way, that makes 12 data warehouse appliances by my count.

A phrase I saw on the internet recently - “Pioneer calls RDBMS technology obsolete” - caught my eye and the first thing that came to mind was “Michael Stonebraker?”. My suspicions were correct. Vertica is his new venture and he states “my prediction is that column stores will take over the warehouse market over time, completely displacing row stores”.

Most IS professionals do not know about column (or “vector”) oriented DBMS. Column-oriented DBMS have several major architectural differences from other relational database management systems. The main difference is its physical orientation of data in columns as opposed to rows. This allows it to perform very high selective compression because all of a column’s values are physically together. It also provides for excellent performance when you select a small subset of the columns in a table since you do not perform I/O for data that is not needed. Column-orientation greatly assists a compression strategy due to the high potential for the existence of similar values in columns of adjacent rows in the table.

The Model 204 was sort of like this and Sybase IQ is definitely column oriented. There have been special occassions where they are more appropriate than the row-oriented DBMS.

It will be interesting to see where and how these approaches find merit in DW, if they have overcome some of the problems of the past such as those below (early indications are that they may have) and finally, if they intend to compete for EDW, as Michael Stonebraker suggests in his quote above.

Former challenges of column-oriented DBMS:

It is recommended and common practice to index all columns at least once and, for some columns, more than once
Lack of parallelism
Query performance disadvantages for any query other than columnar functions
Insert performance disadvantages
Overcoming lack of market resources, lack of vendor ports and industry row-oriented mindsets

Technorati tags: DBMS, ParAccel, Vertica, Calpont


Posted October 5, 2007 8:26 AM
Permalink | No Comments |

Leave a comment

    
   VISIT MY EXPERT CHANNEL

Search this blog
Categories ›
Archives ›
Recent Entries ›