Maintaining internal consistency of report for real-time OLAP with layer-based view
APWeb'11 Proceedings of the 13th Asia-Pacific web conference on Web technologies and applications
Performance optimization of analysis rules in real-time active data warehouses
APWeb'12 Proceedings of the 14th Asia-Pacific international conference on Web Technologies and Applications
Dynamic View Management System for Query Prediction to View Materialization
International Journal of Data Warehousing and Mining
| Hi-index | 0.00 |
A data warehouse is built as a layer on top of existing operational database systems. Once built, it has to be regularly updated (refreshed). Currently, most data warehouse approaches employ static refresh mechanisms whereby updates are based on a static timestamp, eg. once every day/week/quarter only. Whilst for some systems this might be adequate, others require a more rigorous approach ensuring that analysis is always 'up-to-date'. Static time interval for refreshing data warehouse is not adequate enough for systems with high update frequency. A real-time data warehouse incorporates operational data changes in real time. However, sometimes, it is often unnecessary or even inefficient to immediately refresh and send updates from the operational database into a data warehouse. In this paper, we propose a near real-time refresh mechanism that takes into consideration a number of measures: (i) Impact from record, (ii) Number of records affected, and (iii) Frequency Request Measure. The combination of these measures can accurately identify when the data warehouse needs to be strictly real-time, or near real-time (ie. right-time). Our experimentation shows that the proposed approach offers a significant benefit in terms of refresh operation cost in comparison to real-time warehousing, while at the same time still maintaining a high freshness level of the data warehouse.