Andere Kunden interessierten sich auch für
![New Method to Improve Mining of Multi-Class Imbalanced Data]( "New Method to Improve Mining of Multi-Class Imbalanced Data")
New Method to Improve Mining of Multi-Class Imbalanced Data24,99 €![Data Set Modification to Improve ML Algorithm Performance and Speed]( "Data Set Modification to Improve ML Algorithm Performance and Speed")
Data Set Modification to Improve ML Algorithm Performance and Speed27,99 €![Data warehouse model for monitoring key performance indicators (KPIs)]( "Data warehouse model for monitoring key performance indicators (KPIs)")
Data warehouse model for monitoring key performance indicators (KPIs)51,99 €![Use of Data Analytics to Improve Compliance with the Data Privacy Act]( "Use of Data Analytics to Improve Compliance with the Data Privacy Act")
Use of Data Analytics to Improve Compliance with the Data Privacy Act40,99 €![Design of Data-Warehouse for Agriculture]( "Design of Data-Warehouse for Agriculture")
Design of Data-Warehouse for Agriculture51,99 €![A Data warehouse model for Botswana Innovation Hub]( "A Data warehouse model for Botswana Innovation Hub")
A Data warehouse model for Botswana Innovation Hub24,99 €![Data Warehouse Concepts]( "Data Warehouse Concepts")
Data Warehouse Concepts45,99 €
Materialized views can be used in a number of ways. It can be used in distributed databases for replication and can also be used for efficient provision of data to a query through query re- writing. The process of data provision to queries can further be expedited if dependent child views are created on an already existing materialized view. Furthermore, these child-views are automatically created upon the creation of the base materialized view with some restrictions. This results in less-user dependent activity of creation of materialized views based on some parameters. These parameters are the number of child- materialized views and the type of the data a view contain. In this thesis, a balanced approach is suggested to create sub-materialized views to answer user queries without consulting the fact table or parent materialized view that results in avoidance of resource intensive calculations and joining of multiple tables.