System R: Relational Approach to Database Management

Astrahan, M. M.; Blasgen, M. W.; Chamberlin, Donald D.; Eswaran, Kapali P.; Gray, Jim; Griffiths, P. P.; King, William F.; Lorie, Raymond A.; McJones, Paul; Mehl, J. W.; Putzolu, G. R.; Traiger, I. L.; Wade, B. W.; Watson, Vanessa

doi:10.1016/b978-0-934613-53-8.50042-x

Cited by 101 publications

(89 citation statements)

References 21 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…An early approach in this direction was based on adding security services to a general-purpose DBMS, e.g. INGRES [15] or System/R [1]. In fact, many commercial systems use this approach.…”

Section: General Secure Database Systemsmentioning

confidence: 98%

See 1 more Smart Citation

Incorporating Database Systems into a Secure Software Development Methodology

Fernández

Jürjens

Yoshioka

et al. 2008

2008 19th International Conference on Database and Expert Systems Applications

View full text Add to dashboard Cite

We have proposed in the past three separate methodologies for secure software development. We have found that they have many common and complementary aspects and we proposed a combination of them that appears as a good approach to secure software development. The combined methodology applies security at all stages, considers the architectural levels of the system, applies security policies through the use of patterns, and formalizes some portions of the design. We have studied in some detail how to elicit and describe security requirements, how to reflect these requirements in the conceptual model, how to estimate some performance aspects, how to formalize some aspects such as communication protocols, and how to map the conceptual requirements into design artifacts. A design aspect which we have not studied is the incorporation of databases as part of the secure architecture. The database system is a fundamental aspect for security because it stores the persistent information, which constitutes most of the information assets of the institution. We present here some ideas on how to make sure that the database system has the same level of security than the rest of the secure application.

show abstract

“…An early approach in this direction was based on adding security services to a general-purpose DBMS, e.g. INGRES [15] or System/R [1]. In fact, many commercial systems use this approach.…”

Section: General Secure Database Systemsmentioning

confidence: 98%

“…These relations would also store the metadata, including the authorization system of the DBMS. The general architecture of the DBMS could use views [1] or query modification [15] for access enforcement. Views are part of the external schema and usually stored as relations.…”

Section: Domain Analysis Stagementioning

confidence: 99%

Incorporating Database Systems into a Secure Software Development Methodology

Fernández

Jürjens

Yoshioka

et al. 2008

2008 19th International Conference on Database and Expert Systems Applications

View full text Add to dashboard Cite

show abstract

“…Not just the columns of interest are read, but all other columns, too, since row stores usually operate on the granularity of entire tuples (Astrahan et al 1976). This issue has been targeted from two sides: first, optimizations have been developed restructuring the logical data schema, i.e.…”

Section: Mixing the Workloadmentioning

confidence: 99%

A mixed transaction processing and operational reporting benchmark

2010

View full text Add to dashboard Cite

The importance of reporting is ever increasing in today's fast-paced market environments and the availability of up-to-date information for reporting has become indispensable. Current reporting systems are separated from the online transaction processing systems (OLTP) with periodic updates pushed in. A pre-defined and aggregated subset of the OLTP data, however, does not provide the flexibility, detail, and timeliness needed for today's operational reporting. As technology advances, this separation has to be reevaluated and means to study and evaluate new trends in data storage management have to be provided. This article proposes a benchmark for combined OLTP and operational reporting, providing means to evaluate the performance of enterprise data management systems for mixed workloads of OLTP and operational reporting queries. Such systems offer up-to-date information and the flexibility of the entire data set for reporting. We describe how the benchmark provokes the conflicts that are the reason for separating the two workloads on different systems. In this article, we introduce the concepts, logical data schema, transactions and queries of the benchmark, which are entirely based on the orig-A. Bog (B) ·

show abstract

“…The history of advanced transaction models can be traced back to the mechanism of save point, a concept first introduced in [2], which enables a transaction to roll back to an intermediate state. The authors suggest that during the execution of a transaction, a save point can be marked which returns a save point number for subsequent reference.…”

Section: Checkpoints and Save Pointsmentioning

confidence: 99%

A survey on the history of transaction management: from flat to grid transactions

Wang

Vonk

Kratz

et al. 2008

Distrib Parallel Databases

View full text Add to dashboard Cite

Transactions have been around since the Seventies to provide reliable information processing in automated information systems. Originally developed for simple 'debit-credit' style database operations in centralized systems, they have moved into much more complex application domains including aspects like distribution, process-orientation and loose coupling. The amount of published research work on transactions is huge and a number of overview papers and books already exist. A concise historic analysis providing an overview of the various phases of development of transaction models and mechanisms in the context of growing complexity of application domains is still missing, however. To fill this gap, this paper presents a historic overview of transaction models organized in several 'transaction management eras', thereby investigating numerous transaction models ranging from the classical flat transactions, via advanced and workflow transactions to the Web Services and Grid transaction models. The key concepts and techniques with respect to transaction management are investigated. Placing well-known research efforts in historical perspective reveals specific trends and developments in the area of transacRecommended by 236 Distrib Parallel Databases (2008) 23: 235-270 tion management. As such, this paper provides a comprehensive, structured overview of developments in the area.

show abstract

System R: Relational Approach to Database Management

Cited by 101 publications

References 21 publications

Incorporating Database Systems into a Secure Software Development Methodology

Incorporating Database Systems into a Secure Software Development Methodology

A mixed transaction processing and operational reporting benchmark

A survey on the history of transaction management: from flat to grid transactions

Contact Info

Product

Resources

About