Comments for Dataspace http://www.dataspace.com/blog making data make sense Thu, 26 Jan 2012 18:40:23 +0000 hourly 1 Comment on The Myth of Self Service BI by Michael Cole http://www.dataspace.com/blog/the-myth-of-self-service-bi/comment-page-1/#comment-3247 Michael Cole Thu, 26 Jan 2012 18:40:23 +0000 http://dataspace.tumblr.com/post/16006227596#comment-3247 Spot On! Spot On!

]]> Comment on Quiz January, 2012 – The Dreaded Time Zone Question by Timing zone | Calicastillo http://www.dataspace.com/blog/quiz-jan-2012-timezone/comment-page-1/#comment-3243 Timing zone | Calicastillo Thu, 26 Jan 2012 04:56:40 +0000 http://www.dataspace.com/blog/?p=409#comment-3243 [...] QUIZ: Data warehouse time zone data modeling Leave a comment « Witthuhn pronounced Comments are closed. [...] [...] QUIZ: Data warehouse time zone data modeling Leave a comment « Witthuhn pronounced Comments are closed. [...]

]]> Comment on Got BI? Now Become Data Driven by Jordan Martz http://www.dataspace.com/blog/got-bi-now-become-data-driven/comment-page-1/#comment-2853 Jordan Martz Tue, 29 Nov 2011 04:57:40 +0000 http://dataspace.tumblr.com/post/13159668865#comment-2853 It's about enablement from being data-driven,so he gets the value of BI. What about tactical strategy? Predictive analytics enabled by proper governance and data quality. You're just showing the light as a crack in the door to pervasive insight and factual constructs that automate and transcend thought It’s about enablement from being data-driven,so he gets the value of BI. What about tactical strategy? Predictive analytics enabled by proper governance and data quality.

You’re just showing the light as a crack in the door to pervasive insight and factual constructs that automate and transcend thought

]]> Comment on Quiz – July 2011: Hunh? by btaub http://www.dataspace.com/blog/quiz-july-2011-hunh/comment-page-1/#comment-1952 btaub Thu, 14 Jul 2011 12:08:40 +0000 http://www.dataspace.com/blog/?p=382#comment-1952 Fixed! Fixed!

]]> Comment on Quiz – July 2011: Hunh? by kkunkel http://www.dataspace.com/blog/quiz-july-2011-hunh/comment-page-1/#comment-1948 kkunkel Tue, 12 Jul 2011 16:13:25 +0000 http://www.dataspace.com/blog/?p=382#comment-1948 Errors in the quiz . . . "This field requires an unique entry and 'One-to-many relationship' has already been used." upon answering one-to-many relationship in the first multiple choice question of the recent quiz. Good luck, KK Errors in the quiz . . . “This field requires an unique entry and ‘One-to-many relationship’ has already been used.” upon answering one-to-many relationship in the first multiple choice question of the recent quiz.

Good luck,

KK

]]> Comment on Is It Time to Rethink the Concept of the Data Warehouse? by Brian Basolo http://www.dataspace.com/blog/is-it-time-to-rethink-the-concept-of-the-data-warehouse/comment-page-1/#comment-1259 Brian Basolo Tue, 15 Feb 2011 00:42:33 +0000 http://www.dataspace.com/blog/?p=314#comment-1259 The case for Data Warehouse is to create a query optimized view of your operations INDEPENDENT from the structure or logic of the source system(s); capturing and arranging the data as YOU want to view it to support your unique way of doing business. A well designed Data warehouse will survive multiple changes and additions in source system(s). Suppose you are adding new systems, replacing others or are fed up with SAP's mystery database names, thinly disguised ISAM files and high maintenance. So (for example) you move to Oracle e-business where the table and column names are something you can understand. All you need to do is re-write the ET code. Loading from the transformed data into the warehouse would remain unchanged, leaving you with a unbroken view of your operations. The case for Data Warehouse is to create a query optimized view of your operations INDEPENDENT from the structure or logic of the source system(s); capturing and arranging the data as YOU want to view it to support your unique way of doing business.

A well designed Data warehouse will survive multiple changes and additions in source system(s).

Suppose you are adding new systems, replacing others or are fed up with SAP’s mystery database names, thinly disguised ISAM files and high maintenance. So (for example) you move to Oracle e-business where the table and column names are something you can understand. All you need to do is re-write the ET code. Loading from the transformed data into the warehouse would remain unchanged, leaving you with a unbroken view of your operations.

]]> Comment on Is It Time to Rethink the Concept of the Data Warehouse? by Lindsey Niedzielski http://www.dataspace.com/blog/is-it-time-to-rethink-the-concept-of-the-data-warehouse/comment-page-1/#comment-1188 Lindsey Niedzielski Fri, 21 Jan 2011 22:23:34 +0000 http://www.dataspace.com/blog/?p=314#comment-1188 Great post Ben. Thanks for pointing out how liberating integrating your data between systems can be. We have a community for IM professionals (www.openmethodology.org) and have bookmarked this post for our users. Look forward to reading your work in the future. Great post Ben. Thanks for pointing out how liberating integrating your data between systems can be. We have a community for IM professionals (www.openmethodology.org) and have bookmarked this post for our users. Look forward to reading your work in the future.

]]> Comment on Is It Time to Rethink the Concept of the Data Warehouse? by btaub http://www.dataspace.com/blog/is-it-time-to-rethink-the-concept-of-the-data-warehouse/comment-page-1/#comment-1175 btaub Mon, 17 Jan 2011 22:23:18 +0000 http://www.dataspace.com/blog/?p=314#comment-1175 Hi, Bill. Thanks for the comment on the Stipa-Caproni. I knew my subscription to AVIATION HISTORY would pay off sooner or later - regardless of what my wife says :) I like your point about SAP. We're having a similar conversation on a linkedIn forum (http://www.linkedin.com/groups?home=&gid=3342688&trk=anet_ug_hm) and I think I came to a related conclusion. My thought was like this, we have DW appliance vendors building appliances that are optimized for reporting but can't handle OLTP. Perhaps they should be looking at how to build appliances that can address OLTP but can also attack reporting. Maybe these appliances require additional data structures, etc. but they hide those structures from users and developers. Anyhow, thanks again for your input! -- Ben Hi, Bill. Thanks for the comment on the Stipa-Caproni. I knew my subscription to AVIATION HISTORY would pay off sooner or later – regardless of what my wife says :)

I like your point about SAP. We’re having a similar conversation on a linkedIn forum (http://www.linkedin.com/groups?home=&gid=3342688&trk=anet_ug_hm) and I think I came to a related conclusion. My thought was like this, we have DW appliance vendors building appliances that are optimized for reporting but can’t handle OLTP. Perhaps they should be looking at how to build appliances that can address OLTP but can also attack reporting. Maybe these appliances require additional data structures, etc. but they hide those structures from users and developers.

Anyhow, thanks again for your input!

– Ben

]]> Comment on Is It Time to Rethink the Concept of the Data Warehouse? by Bill Jacobs http://www.dataspace.com/blog/is-it-time-to-rethink-the-concept-of-the-data-warehouse/comment-page-1/#comment-1174 Bill Jacobs Mon, 17 Jan 2011 21:46:04 +0000 http://www.dataspace.com/blog/?p=314#comment-1174 P.S. This is the very first use I've seen of photo a Stipa-Caproni in anything other than an aviation pub. GREAT analogy. P.S.

This is the very first use I’ve seen of photo a Stipa-Caproni in anything other than an aviation pub. GREAT analogy.

]]> Comment on Is It Time to Rethink the Concept of the Data Warehouse? by Bill Jacobs http://www.dataspace.com/blog/is-it-time-to-rethink-the-concept-of-the-data-warehouse/comment-page-1/#comment-1173 Bill Jacobs Mon, 17 Jan 2011 21:43:20 +0000 http://www.dataspace.com/blog/?p=314#comment-1173 I think perhaps you have the right conclusion, but upside down. Consider this. How many times is a piece of transaction data "touched" during transactions (e.g. the reason we do OLTP solutions in the first place...)? And consider the alternative - how many times is it "touched" directly, or as part of an aggregate, in a report, a dashboard, a historic analysis, a customer scoring activity, a fraud report, an inquiry or one of the other activites we stood the warehouses, ODSs and marts up for in the first place? Look at HANA from SAP - and read its history, and you see Hisso Plattner (founder of SAP) proposing something akin to a warehouse that ends the need for OLTP stores (rather than the other way around...). And one of the vehicles - could it be - noSQL stores that only exist for initial reliable capture of the transaction? Bill So is it perhaps that transactional storage that needs to be folded into what we today call the ODS or warehouse (yes, I know they're not the same...). Bill I think perhaps you have the right conclusion, but upside down.

Consider this. How many times is a piece of transaction data “touched” during transactions (e.g. the reason we do OLTP solutions in the first place…)?

And consider the alternative – how many times is it “touched” directly, or as part of an aggregate, in a report, a dashboard, a historic analysis, a customer scoring activity, a fraud report, an inquiry or one of the other activites we stood the warehouses, ODSs and marts up for in the first place?

Look at HANA from SAP – and read its history, and you see Hisso Plattner (founder of SAP) proposing something akin to a warehouse that ends the need for OLTP stores (rather than the other way around…). And one of the vehicles – could it be – noSQL stores that only exist for initial reliable capture of the transaction?

Bill

So is it perhaps that transactional storage that needs to be folded into what we today call the ODS or warehouse (yes, I know they’re not the same…).

Bill

]]>