A Diy Approach to Uni-Temporal Database Implementation
L. Haitao Yang Fei Xu. International Journal of Advanced Computer Science and Applications(IJACSA), (2013)
Abstract
when historical versions of data are concerned for a MIS (Management Information System) we naturally might resort to temporal database products. These bi-temporal products, however, are often extravagant and not easily mastered to most of MIS practitioners. Hence we present a plain DIY (do it yourself) solution, the Audit & Change Logs Mechanism-based approach--ACLM, to meet the uni-temporal requirement from restoring historical versions of data. With ACLM programmers can code SQL scripts on demand to trace and replay any snapshot of historical data version via RDBMS built-in functions, they need not to shift away from their usual way of coding stored procedures for data maintenance. Besides, the ACLM approach is compatible with mega-data change, and its additive overhead was instantiated imperceptible for throughputs of routine access with a typical scenario.
%0 Journal Article
%1 IJACSA.2013.040919
%A Haitao Yang Fei Xu, Lating Xia
%D 2013
%J International Journal of Advanced Computer Science and Applications(IJACSA)
%K DIY MIS database; historical recurrence; snapshot; solution; uni-temporal
%N 9
%T A Diy Approach to Uni-Temporal Database Implementation
%U http://ijacsa.thesai.org/
%V 4
%X when historical versions of data are concerned for a MIS (Management Information System) we naturally might resort to temporal database products. These bi-temporal products, however, are often extravagant and not easily mastered to most of MIS practitioners. Hence we present a plain DIY (do it yourself) solution, the Audit & Change Logs Mechanism-based approach--ACLM, to meet the uni-temporal requirement from restoring historical versions of data. With ACLM programmers can code SQL scripts on demand to trace and replay any snapshot of historical data version via RDBMS built-in functions, they need not to shift away from their usual way of coding stored procedures for data maintenance. Besides, the ACLM approach is compatible with mega-data change, and its additive overhead was instantiated imperceptible for throughputs of routine access with a typical scenario.
@article{IJACSA.2013.040919,
abstract = {when historical versions of data are concerned for a MIS (Management Information System) we naturally might resort to temporal database products. These bi-temporal products, however, are often extravagant and not easily mastered to most of MIS practitioners. Hence we present a plain DIY (do it yourself) solution, the Audit \& Change Logs Mechanism-based approach--ACLM, to meet the uni-temporal requirement from restoring historical versions of data. With ACLM programmers can code SQL scripts on demand to trace and replay any snapshot of historical data version via RDBMS built-in functions, they need not to shift away from their usual way of coding stored procedures for data maintenance. Besides, the ACLM approach is compatible with mega-data change, and its additive overhead was instantiated imperceptible for throughputs of routine access with a typical scenario.},
added-at = {2014-02-21T08:00:08.000+0100},
author = {{Haitao Yang Fei Xu}, Lating Xia},
biburl = {https://www.bibsonomy.org/bibtex/25d478d808ed985acff082d9919f9a6b4/thesaiorg},
interhash = {b245c357b34a267bcf23e19bb7eb7f18},
intrahash = {5d478d808ed985acff082d9919f9a6b4},
journal = {International Journal of Advanced Computer Science and Applications(IJACSA)},
keywords = {DIY MIS database; historical recurrence; snapshot; solution; uni-temporal},
number = 9,
timestamp = {2014-02-21T08:00:08.000+0100},
title = {{A Diy Approach to Uni-Temporal Database Implementation}},
url = {http://ijacsa.thesai.org/},
volume = 4,
year = 2013
}