ACM Home Page
Please provide us with feedback. Feedback
Records retention in relational database systems
Full text PdfPdf (421 KB)
Source
Conference on Information and Knowledge Management archive
Proceeding of the 17th ACM conference on Information and knowledge management table of contents
Napa Valley, California, USA
SESSION: DB: security and privacy table of contents
Pages 873-882  
Year of Publication: 2008
ISBN:978-1-59593-991-3
Authors
Ahmed A. Ataullah  University of Waterloo, Waterloo, ON, Canada
Ashraf Aboulnaga  University of Waterloo, Waterloo, ON, Canada
Frank Wm. Tompa  University of Waterloo, David R. Cheriton School of Co, ON, Canada
Sponsors
ACM: Association for Computing Machinery
SIGWEB: ACM Special Interest Group on Hypertext, Hypermedia, and Web
SIGIR: ACM Special Interest Group on Information Retrieval
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 17,   Downloads (12 Months): 178,   Citation Count: 0
Additional Information:

abstract   references   index terms   collaborative colleagues  

Tools and Actions: Request Permissions Request Permissions    Review this Article  
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/1458082.1458197
What is a DOI?

ABSTRACT

The recent introduction of several pieces of legislation mandating minimum and maximum retention periods for corporate records has prompted the Enterprise Content Management (ECM) community to develop various records retention solutions. Records retention is a significant subfield of records management, and legal records retention requirements apply over corporate records regardless of their shape or form. Unfortunately, the scope of existing solutions has been largely limited to proper identification, classification and retention of documents, and not of data more generally.

In this paper we address the problem of managed records retention in the context of relational database systems. The problem is significantly more challenging than it is for documents for several reasons. Foremost, there is no clear definition of what constitutes a business record in relational databases; it could be an entire table, a tuple, part of a tuple, or parts of several tuples from multiple tables. There are also no standardized mechanisms for purging, anonymizing and protecting relational records. Functional dependencies, user defined constraints, and side effects caused by triggers make it even harder to guarantee that any given record will actually be protected when it needs to be protected or expunged when the necessary conditions are met. Most importantly, relational tuples may be organized such that one piece of data may be part of various legal records and subject to several (possibly conflicting) retention policies.

We address the above problems and present a complete solution for designing, managing, and enforcing records retention policies in relational database systems. We experimentally demonstrate that the proposed framework can guarantee compliance with a broad range of retention policies on an off-the-shelf system without incurring a significant performance overhead for policy monitoring and enforcement.


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
United States Public Company Accounting Reform and Investor Protection Act of 2002 (Sarbanes-Oxley Act) (Pub.L. 107-204, 116 Stat. 745). August 2002.
 
2
 
3
4
 
5
Ahmed Ataullah. A Framework for Records Management in Relational Database Management Systems. Master's thesis, University of Waterloo, Waterloo, Ontario, Canada, April 2008.
 
6
7
 
8
 
9
10
 
11
 
12
Eric N. Hanson, Chris Carnes, Lan Huang, Mohan Konyala, Lloyd Noronha, Sashi Parthasarathy, J. B. Park, and Albert Vernon. Scalable trigger processing. In ICDE, 1999.
 
13
 
14
Bill Lipner. The million-dollar backup tape. ComputerWorld Magazine, August 2006.
 
15
Claudia Bauzer Medeiros and Frank Wm. Tompa. Understanding the implications of view update policies. Algorithmica, 1986.
 
16
Marco C. Mont and Robert Thyne. A System to Handle Privacy Obligations in Enterprises. In Hewlett-Packard Internal Technical Report (HPL-2005-180), 2005.
17
18
 
19

Collaborative Colleagues:
Ahmed A. Ataullah: colleagues
Ashraf Aboulnaga: colleagues
Frank Wm. Tompa: colleagues