Suppose that a data warehouse contains 20 dimensions, each with about five levels of granularity. (a) Users are mainly interested in four particular dimensions, each having three frequently accessed levels for rolling up and drilling down. How would you design a data cube structure to support this preference efficiently? (b) At times, a user may want to drill through the cube, down to the raw data for one or two particular dimensions. How would you support this feature?

Suppose that a data warehouse contains 20 dimensions, each with about five levels of granularity. (a) Users are mainly interested in four particular dimensions, each having three frequently accessed levels for rolling up and drilling down. How would you design a data cube structure to support this preference efficiently? (b) At times, a user may want to drill through the cube, down to the raw data for one or two particular dimensions. How would you support this feature?

MIS

9th Edition

ISBN:9781337681919

Author:BIDGOLI

Publisher:BIDGOLI

Chapter3: Database Systems, Data Warehouses, And Data Marts

Section: Chapter Questions

Problem 3AYRM

See similar textbooks

Similar questions

Suppose your task as a software engineer at Big-University is to design a data mining system to examine their university course database, which contains the following information: the name, address. And status (e.g.. undergraduate or graduate) of each student, the courses taken, and their cumulative grade point average (GPA). Describe the architecture you would choose. What is the purpose of each component of this architecture.
The most important component of the architecture is the MetaData component. This is because it is the most critical component of the data warehouse design.
When it comes to data collection in a warehouse, what are the pros and cons of using a source-driven architecture as opposed to a destination-driven design?
What are the advantages and disadvantages of a destination-driven design vs a source-driven architecture for data collection in a data warehouse?
What are the benefits and drawbacks of a source-driven architecture vs a destination-driven design for data collecting in a data warehouse?
What are the advantages and disadvantages of a source-driven architecture vs a destination-driven design for gathering data in a data warehouse?
Is it better to use a source-driven architecture or a destination-driven architecture to collect data in a warehouse? What are the pros and cons of each?
Take, for example, a database that is used by a large airline and in which the underlying database management system utilises snapshot isolation. In spite of the fact that the airline would prefer a serializable execution, it could be ready to tolerate a non serializable execution if it means that the process would be completed more quickly overall.
Explain the advantages of using "Schema Evolution" in serialized data formats.
Consider, for instance, the database management system that is used by an airline; such a system often has snapshot isolation as one of its many capabilities. I was hoping that you could provide me an example of a non-serializable execution that the airline is ready to endure in order to get better performance as a whole. If you could, that would be much appreciated.
The three-layer architecture has the primary objective of separating each user’s view of the database from the way it is physically represented. Using an example database architecture of your own, answer the following questions: Provide an example of a structure at each of the three-levels Using the answer from a) above, describe physical data independence
In the context of handler interfaces, how is caching managed to ensure data freshness while optimizing performance?