Agile Enterprise Data Warehousing
2 posters
Page 1 of 1
Agile Enterprise Data Warehousing
I would really appreciate it if someone could just point me in the right direction with regards the situation I’m faced with currently.
The scenario:
My team was tasked with implementing a data warehouse.
This has been a challenge since the environment is full of very clever people who have an inherent love for relational data models and object-orientated design approaches. However, through many workshops and presentations at Architectural committees ect ... we have clearly explained the beauty of dimensional modelling. We have designed the entire process, from ETL 1 (staging) to ETL 2 (data warehouse) including bus matrix, we have a dimensional model which already we have partly tested with data loads and our reports are reconciling.
The issue:
So we thought we were set and ready to go and then came the politics!
Before we have even finished development the management/architects now want another team with virtually no experience to develop in parallel another data mart that needs to leverage off our conformed dimensions. This also includes them using a different schema developing in our same staging database and also loading into our same data warehouse database. So now we have been tasked to define the business process of how such collaboration can occur, so that the new people can follow the template and process.
My questions:
I came across design tip #111 Is Agile Enterprise Data Warehousing an Oxymoron. This article seems to be the process I need to define.
First, do you think this is practically possible?
Secondly, could you point me in the right direction in defining this environment?
Thirdly, people have been telling me that Ralph Kimball has designed the “Data Warehouse Bus Structure”. Enabling almost a virtual data warehouse environment where data mart could be located on different servers, yet still enabling enterprise reporting on top of it, with the required performance. Do you have any articles or guiding principles that I need to consider before putting forward recommendations?
The scenario:
My team was tasked with implementing a data warehouse.
This has been a challenge since the environment is full of very clever people who have an inherent love for relational data models and object-orientated design approaches. However, through many workshops and presentations at Architectural committees ect ... we have clearly explained the beauty of dimensional modelling. We have designed the entire process, from ETL 1 (staging) to ETL 2 (data warehouse) including bus matrix, we have a dimensional model which already we have partly tested with data loads and our reports are reconciling.
The issue:
So we thought we were set and ready to go and then came the politics!
Before we have even finished development the management/architects now want another team with virtually no experience to develop in parallel another data mart that needs to leverage off our conformed dimensions. This also includes them using a different schema developing in our same staging database and also loading into our same data warehouse database. So now we have been tasked to define the business process of how such collaboration can occur, so that the new people can follow the template and process.
My questions:
I came across design tip #111 Is Agile Enterprise Data Warehousing an Oxymoron. This article seems to be the process I need to define.
First, do you think this is practically possible?
Secondly, could you point me in the right direction in defining this environment?
Thirdly, people have been telling me that Ralph Kimball has designed the “Data Warehouse Bus Structure”. Enabling almost a virtual data warehouse environment where data mart could be located on different servers, yet still enabling enterprise reporting on top of it, with the required performance. Do you have any articles or guiding principles that I need to consider before putting forward recommendations?
Justin Lovell- Posts : 1
Join date : 2011-02-03
Re: Agile Enterprise Data Warehousing
Develop dimensional modeling standards, ETL standards, and database standards, to ensure the new group designs their process correctly. If you sit back, this looks like a good thing. The DW is gaining acceptance across the enterprise. Once standards are in place, make sure you review their work to ensure it is compliant with existing DW structures, ETL, etc.
BoxesAndLines- Posts : 1212
Join date : 2009-02-03
Location : USA
Similar topics
» Agile Data Warehousing - DEsign Tip 111
» How to implement a data warehousing solution for Google Analytics data?
» Agile BI - Data Model
» SOA and Data Warehousing
» New to Data warehousing
» How to implement a data warehousing solution for Google Analytics data?
» Agile BI - Data Model
» SOA and Data Warehousing
» New to Data warehousing
Page 1 of 1
Permissions in this forum:
You cannot reply to topics in this forum