SEP 9, 2013 11:39am ET

Related Links

Conn. Attorney General Wants to Talk Privacy with Apple
September 17, 2014
Big Data Gets Bigger Footprint in Insurance
September 16, 2014
More Than 75 Percent of Mobile Apps Will Fail Basic Security Tests
September 16, 2014

Web Seminars

Why Data Virtualization Can Save the Data Warehouse
Available On Demand
Essential Guide to Using Data Virtualization for Big Data Analytics
September 24, 2014

Big Data Changed the Way We Think About Data Warehousing


Expectations from organizations have changed the demand for data.

Get access to this article and thousands more...

All Information Management articles are archived after 7 days. REGISTER NOW for unlimited access to all recently archived articles, as well as thousands of searchable stories. Registered Members also gain access to:

  • Full access to including all searchable archived content
  • Exclusive E-Newsletters delivering the latest headlines to your inbox
  • Access to White Papers, Web Seminars, and Blog Discussions
  • Discounts to upcoming conferences & events
  • Uninterrupted access to all sponsored content, and MORE!

Already Registered?


Comments (5)
Sorry if my comment is a bit of advertising, but the article states "It can be difficult to modify and maintain the data warehouse once it is implemented and the business decides to change. " - if the data warehouse was built using WhereScape RED, which prefers ELT and generates and maintains SQL code, while auto-documenting, then this hurdle is easily overcome. Because of full data lineage in the documentation up and downstream change impact is easy to calculate, and we have found our customers are able to effect changes in days rather than months.
Posted by Leon B | Tuesday, September 10 2013 at 8:09AM ET
Hello Michael,

The questions you pose are certainly relevant. There are a number of alternative methods out there that support "today's data warehouse". Many of these do handle, and have handled Big Data for years. Most of the new methods are based on Agile project methodologies coupled with specific modeling paradigms.

To name a few, there is a Hub and Spoke modeling approach called the Data Vault which has been in use for over 13 years now. There is another modeling method called Anchor Modeling, another called Head / Tail, and so on...

There are a huge number of changes in the market space making it possible for "today's" data warehouse to be completely different than one constructed just a year ago.

In the end, it will be (as it always has been) How do we provide value to the business, as fast as possible, with the highest quality and most flexibility?

The technology underneath will continue to merge (become seamless) and over the next two or three years we (data / systems architects) will neither know nor care where the data sets are stored. Most of the "database management systems" will become hybridized, and offer the best of all worlds, or perhaps a mediocre balance of all.

An additional thought is: Textual Analytics, Semantic analysis, Semantic modeling, Ontologies of business terms, and multi-structured information.

Thanks for an interesting article, would love to see it expanded.

Cheers, Dan Linstedt Anyone interested in Data Vault 2.0 can check it out at:

Posted by Dan L | Tuesday, September 10 2013 at 8:16AM ET
Add Your Comments:
You must be registered to post a comment.
Not Registered?
You must be registered to post a comment. Click here to register.
Already registered? Log in here
Please note you must now log in with your email address and password.
Login  |  My Account  |  White Papers  |  Web Seminars  |  Events |  Newsletters |  eBooks
Please note you must now log in with your email address and password.