|
ABSTRACT
Supporting graceful schema evolution represents an unsolved problem for traditional information systems that is further exacerbated in web information systems, such as Wikipedia and public scientific databases: in these projects based on multiparty cooperation the frequency of database schema changes has increased while tolerance for downtimes has nearly disappeared. As of today, schema evolution remains an error-prone and time-consuming undertaking, because the DB Administrator (DBA) lacks the methods and tools needed to manage and automate this endeavor by (i) predicting and evaluating the effects of the proposed schema changes, (ii) rewriting queries and applications to operate on the new schema, and (iii) migrating the database. Our PRISM system takes a big first step toward addressing this pressing need by providing: (i) a language of Schema Modification Operators to express concisely complex schema changes, (ii) tools that allow the DBA to evaluate the effects of such changes, (iii) optimized translation of old queries to work on the new schema version, (iv) automatic data migration, and (v) full documentation of intervened changes as needed to support data provenance, database flash back, and historical queries. PRISM solves these problems by integrating recent theoretical advances on mapping composition and invertibility, into a design that also achieves usability and scalability. Wikipedia and its 170+ schema versions provided an invaluable testbed for validating PRISM tools and their ability to support legacy queries.
REFERENCES
Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.
| |
1
|
R. B. Almeida, B. Mozafari, and J. Cho. On the evolution of wikipedia. In Int. Conf. on Weblogs and Social Media, March 2007.
|
| |
2
|
|
| |
3
|
P. A. Bernstein. Applying model management to classical meta data problems. In CIDR, 2003.
|
| |
4
|
|
| |
5
|
P. A. Bernstein and E. Rahm. Data warehouse scenarios for model management. In ER, 2003.
|
| |
6
|
|
| |
7
|
A. Cleve and J.-L. Hainaut. Co-transformations in database applications evolution. Generative and Transformational Techniques in Software Engineering, pages 409--421, 2006.
|
| |
8
|
C. A. Curino, H. J. Moon, L. Tanca, and C. Zaniolo. Schema Evolution in Wikipedia: toward a Web Information System Benchmark. ICEIS, 2008.
|
| |
9
|
C. A. Curino, H. J. Moon, and C. Zaniolo. Managing the history of metadata in support for db archiving and schema evolution. In ECDM, 2008.
|
| |
10
|
DB2 development team. DB2 Change Management Expert. 2006.
|
| |
11
|
|
| |
12
|
|
 |
13
|
|
 |
14
|
|
 |
15
|
|
| |
16
|
|
| |
17
|
M. Golfarelli, J. Lechtenbörger, S. Rizzi, and G. Vossen. Schema versioning in data warehouses. In ER (Workshops), pages 415--428, 2004.
|
| |
18
|
|
| |
19
|
|
| |
20
|
T. Lemke and R. Manthey. The schema evolution assistant: Tool description, 1995.
|
| |
21
|
|
 |
22
|
|
| |
23
|
|
 |
24
|
|
 |
25
|
|
| |
26
|
Oracle development team. Oracle database 10g online data reorganization and redefinition. 2005.
|
| |
27
|
Y.-G. Ra. Relational schema evolution for program independency. Intelligent Information Technology, pages 273--281, 2005.
|
| |
28
|
S. Rizzi and M. Golfarelli. X-time: Schema versioning and cross-version querying in data warehouses. In ICDE, pages 1471--1472, 2007.
|
| |
29
|
J. Roddick. A Survey of Schema Versioning Issues for Database Systems. Information and Software Technology, 37(7):383--393, 1995.
|
| |
30
|
|
| |
31
|
|
| |
32
|
Wikimedia Foundation. Mediawiki http://www.mediawiki.org, 2007. {Online}.
|
| |
33
|
Wikimedia Foundation. Wikipedia http://en.wikipedia.org/, 2007. {Online}.
|
| |
34
|
|
CITED BY 2
|
|
Hyun J. Moon , Carlo A. Curino , Myungwon Ham , Carlo Zaniolo, PRIMA: archiving and querying historical data with evolving schemas, Proceedings of the 35th SIGMOD international conference on Management of data, June 29-July 02, 2009, Providence, Rhode Island, USA
|
|
|
|
|