No Shortcuts: Focus on DW/BI Architecture and Processes, then Think about the Tools

December 18, 2009
49 Views

No_shortcut A common problem from an IT perspective is the perception that BI is just about learning how to use the tools such as databases, ETL, reporting and online analytical processing (OLAP).  You use a carpenter to build your house, but you need an architect to design it. Simply knowing how to mechanically use the tools does not help you in designing the database(s), ETL loads or dashboards.

This problem is especially pronounced when the BI or ETL tool is free because it is either bundled with other software such as a database or distributed as open source software (OSS). Often project teams are frustrated with these free tools and the project fails. But those are just symptoms. The real problem is that the team didn’t read the instructions.

The first issue is often that members of the IT staff teach themselves how to use the tools. Just as “he who is his own lawyer has a fool for a client,” an IT person who has never done BI or ETL can only teach herself the mechanics (the what) of the tools but not the how. A self-taught developer inevitably tries to use the tool as she would if she were hand-coding… big mistake.

The second and bigger issue, the project team



No_shortcut A common problem from an IT perspective is the perception that BI is just about learning how to use the tools such as databases, ETL, reporting and online analytical processing (OLAP).  You use a carpenter to build your house, but you need an architect to design it. Simply knowing how to mechanically use the tools does not help you in designing the database(s), ETL loads or dashboards.

This problem is especially pronounced when the BI or ETL tool is free because it is either bundled with other software such as a database or distributed as open source software (OSS). Often project teams are frustrated with these free tools and the project fails. But those are just symptoms. The real problem is that the team didn’t read the instructions.

The first issue is often that members of the IT staff teach themselves how to use the tools. Just as “he who is his own lawyer has a fool for a client,” an IT person who has never done BI or ETL can only teach herself the mechanics (the what) of the tools but not the how. A self-taught developer inevitably tries to use the tool as she would if she were hand-coding… big mistake.

The second and bigger issue, the project team and their sponsor figure that free tools mean no investment is necessary, so they never get trained in the concepts. Data warehousing is complicated; you have to understand why you build warehouses, how you design them and what the processes are to load, cleanse and access them.

(For more on this series, see No Shortcuts: Read the BI/DW Instructions and Ask for Directions.)


Link to original post

You may be interested

How SAP Hana is Driving Big Data Startups
Big Data
298 shares3,139 views
Big Data
298 shares3,139 views

How SAP Hana is Driving Big Data Startups

Ryan Kh - July 20, 2017

The first version of SAP Hana was released in 2010, before Hadoop and other big data extraction tools were introduced.…

Data Erasing Software vs Physical Destruction: Sustainable Way of Data Deletion
Data Management
120 views
Data Management
120 views

Data Erasing Software vs Physical Destruction: Sustainable Way of Data Deletion

Manish Bhickta - July 20, 2017

Physical Data destruction techniques are efficient enough to destroy data, but they can never be considered eco-friendly. On the other…

10 Simple Rules for Creating a Good Data Management Plan
Data Management
69 shares689 views
Data Management
69 shares689 views

10 Simple Rules for Creating a Good Data Management Plan

GloriaKopp - July 20, 2017

Part of business planning is arranging how data will be used in the development of a project. This is why…