To speed up on-line analytical processing (OLAP), data warehouse, which is usually derived from operational databases, is introduced. When the operational databases happen to change, the data warehouse gets stale. To maintain the freshness of data warehouse, operational database changes need to be frequently and concurrently propagated into the data warehouse. However, if several update transactions are allowed to execute concurrently without an appropriate concurrency control, data inconsistency between data warehouse and operational databases could arise due to incorrect propagation of changes on the operational databases into the data warehouse. In this paper, we propose a new concurrency control scheme, which could execute a number of update transactions in a consistent way. Whenever an update transaction tries to update a data that is being used by OLAP transactions, our scheme allows the update transaction to create a new version of the data. To investigate the applicable areas of our scheme, its performance is evaluated by means of simulation approach. Our experimental results show that the proposed scheme enables OLAP transactions to continuously read a very fresh data without wasting a lot of time to find out an appropriate version of the data from the version pool.
The copyright of the original papers published on this site belongs to IEICE. Unauthorized use of the original or translated papers is prohibited. See IEICE Provisions on Copyright for details.
Copy
Jinbae KIM, Songchun MOON, "Performance of Concurrency Control Schemes in Data Warehousing Systems" in IEICE TRANSACTIONS on Information,
vol. E86-D, no. 11, pp. 2395-2406, November 2003, doi: .
Abstract: To speed up on-line analytical processing (OLAP), data warehouse, which is usually derived from operational databases, is introduced. When the operational databases happen to change, the data warehouse gets stale. To maintain the freshness of data warehouse, operational database changes need to be frequently and concurrently propagated into the data warehouse. However, if several update transactions are allowed to execute concurrently without an appropriate concurrency control, data inconsistency between data warehouse and operational databases could arise due to incorrect propagation of changes on the operational databases into the data warehouse. In this paper, we propose a new concurrency control scheme, which could execute a number of update transactions in a consistent way. Whenever an update transaction tries to update a data that is being used by OLAP transactions, our scheme allows the update transaction to create a new version of the data. To investigate the applicable areas of our scheme, its performance is evaluated by means of simulation approach. Our experimental results show that the proposed scheme enables OLAP transactions to continuously read a very fresh data without wasting a lot of time to find out an appropriate version of the data from the version pool.
URL: https://global.ieice.org/en_transactions/information/10.1587/e86-d_11_2395/_p
Copy
@ARTICLE{e86-d_11_2395,
author={Jinbae KIM, Songchun MOON, },
journal={IEICE TRANSACTIONS on Information},
title={Performance of Concurrency Control Schemes in Data Warehousing Systems},
year={2003},
volume={E86-D},
number={11},
pages={2395-2406},
abstract={To speed up on-line analytical processing (OLAP), data warehouse, which is usually derived from operational databases, is introduced. When the operational databases happen to change, the data warehouse gets stale. To maintain the freshness of data warehouse, operational database changes need to be frequently and concurrently propagated into the data warehouse. However, if several update transactions are allowed to execute concurrently without an appropriate concurrency control, data inconsistency between data warehouse and operational databases could arise due to incorrect propagation of changes on the operational databases into the data warehouse. In this paper, we propose a new concurrency control scheme, which could execute a number of update transactions in a consistent way. Whenever an update transaction tries to update a data that is being used by OLAP transactions, our scheme allows the update transaction to create a new version of the data. To investigate the applicable areas of our scheme, its performance is evaluated by means of simulation approach. Our experimental results show that the proposed scheme enables OLAP transactions to continuously read a very fresh data without wasting a lot of time to find out an appropriate version of the data from the version pool.},
keywords={},
doi={},
ISSN={},
month={November},}
Copy
TY - JOUR
TI - Performance of Concurrency Control Schemes in Data Warehousing Systems
T2 - IEICE TRANSACTIONS on Information
SP - 2395
EP - 2406
AU - Jinbae KIM
AU - Songchun MOON
PY - 2003
DO -
JO - IEICE TRANSACTIONS on Information
SN -
VL - E86-D
IS - 11
JA - IEICE TRANSACTIONS on Information
Y1 - November 2003
AB - To speed up on-line analytical processing (OLAP), data warehouse, which is usually derived from operational databases, is introduced. When the operational databases happen to change, the data warehouse gets stale. To maintain the freshness of data warehouse, operational database changes need to be frequently and concurrently propagated into the data warehouse. However, if several update transactions are allowed to execute concurrently without an appropriate concurrency control, data inconsistency between data warehouse and operational databases could arise due to incorrect propagation of changes on the operational databases into the data warehouse. In this paper, we propose a new concurrency control scheme, which could execute a number of update transactions in a consistent way. Whenever an update transaction tries to update a data that is being used by OLAP transactions, our scheme allows the update transaction to create a new version of the data. To investigate the applicable areas of our scheme, its performance is evaluated by means of simulation approach. Our experimental results show that the proposed scheme enables OLAP transactions to continuously read a very fresh data without wasting a lot of time to find out an appropriate version of the data from the version pool.
ER -