Performance Analysis of "What-If" Databases Using Independently Updated Views

Richard G. Ramirez, Uday Kulkarni, Kathleen A. Moser

Research output: Contribution to journalArticle

3 Citations (Scopus)

Abstract

Multiple scenarios are critical to "what-if' analysis. Scenarios are built using alternate versions of a database; each version shows, in detail, the result of a decision or a combination of decisions. Relational database management systems, despite their widespread use, lack the explicit capabilities for what-if analysis. We present a concept called independently updated views (IUVs) for creating multiple scenarios. An IUV corresponds to a version of the database. Each version is manipulated and updated as if it were the "real" database; however, only differences between the version and the real database are stored. This paper describes an experiment for measuring the overhead of using IUVs for supporting what-if analysis for a range of typical views and queries. Results indicate that the overhead is minimal for creating what-if scenarios based on views with aggregate functions (SUM, AVG) and on views that are small subsets of the database. These are the classes of views that are more often used in decision making. For views that require retrieval of entire or large portions of the database, the overhead can be high and special data structures may be required.

Original languageEnglish (US)
Pages (from-to)185-203
Number of pages19
JournalJournal of Management Information Systems
Volume9
Issue number1
StatePublished - Jun 1992

Fingerprint

Data base
Performance analysis
Data structures
Decision making
Scenarios
Experiments
Relational database
Query
Database management systems
Experiment

Keywords

  • "What-if' analysis
  • Hypothetical databases
  • Relational databases
  • Relational views
  • View updates

ASJC Scopus subject areas

  • Management Information Systems
  • Information Systems and Management
  • Management Science and Operations Research
  • Computer Science Applications

Cite this

Performance Analysis of "What-If" Databases Using Independently Updated Views. / Ramirez, Richard G.; Kulkarni, Uday; Moser, Kathleen A.

In: Journal of Management Information Systems, Vol. 9, No. 1, 06.1992, p. 185-203.

Research output: Contribution to journalArticle

@article{5ebc2ea9373c44f59f59f3adb079a5d6,
title = "Performance Analysis of {"}What-If{"} Databases Using Independently Updated Views",
abstract = "Multiple scenarios are critical to {"}what-if' analysis. Scenarios are built using alternate versions of a database; each version shows, in detail, the result of a decision or a combination of decisions. Relational database management systems, despite their widespread use, lack the explicit capabilities for what-if analysis. We present a concept called independently updated views (IUVs) for creating multiple scenarios. An IUV corresponds to a version of the database. Each version is manipulated and updated as if it were the {"}real{"} database; however, only differences between the version and the real database are stored. This paper describes an experiment for measuring the overhead of using IUVs for supporting what-if analysis for a range of typical views and queries. Results indicate that the overhead is minimal for creating what-if scenarios based on views with aggregate functions (SUM, AVG) and on views that are small subsets of the database. These are the classes of views that are more often used in decision making. For views that require retrieval of entire or large portions of the database, the overhead can be high and special data structures may be required.",
keywords = "{"}What-if' analysis, Hypothetical databases, Relational databases, Relational views, View updates",
author = "Ramirez, {Richard G.} and Uday Kulkarni and Moser, {Kathleen A.}",
year = "1992",
month = "6",
language = "English (US)",
volume = "9",
pages = "185--203",
journal = "Journal of Management Information Systems",
issn = "0742-1222",
publisher = "M.E. Sharpe Inc.",
number = "1",

}

TY - JOUR

T1 - Performance Analysis of "What-If" Databases Using Independently Updated Views

AU - Ramirez, Richard G.

AU - Kulkarni, Uday

AU - Moser, Kathleen A.

PY - 1992/6

Y1 - 1992/6

N2 - Multiple scenarios are critical to "what-if' analysis. Scenarios are built using alternate versions of a database; each version shows, in detail, the result of a decision or a combination of decisions. Relational database management systems, despite their widespread use, lack the explicit capabilities for what-if analysis. We present a concept called independently updated views (IUVs) for creating multiple scenarios. An IUV corresponds to a version of the database. Each version is manipulated and updated as if it were the "real" database; however, only differences between the version and the real database are stored. This paper describes an experiment for measuring the overhead of using IUVs for supporting what-if analysis for a range of typical views and queries. Results indicate that the overhead is minimal for creating what-if scenarios based on views with aggregate functions (SUM, AVG) and on views that are small subsets of the database. These are the classes of views that are more often used in decision making. For views that require retrieval of entire or large portions of the database, the overhead can be high and special data structures may be required.

AB - Multiple scenarios are critical to "what-if' analysis. Scenarios are built using alternate versions of a database; each version shows, in detail, the result of a decision or a combination of decisions. Relational database management systems, despite their widespread use, lack the explicit capabilities for what-if analysis. We present a concept called independently updated views (IUVs) for creating multiple scenarios. An IUV corresponds to a version of the database. Each version is manipulated and updated as if it were the "real" database; however, only differences between the version and the real database are stored. This paper describes an experiment for measuring the overhead of using IUVs for supporting what-if analysis for a range of typical views and queries. Results indicate that the overhead is minimal for creating what-if scenarios based on views with aggregate functions (SUM, AVG) and on views that are small subsets of the database. These are the classes of views that are more often used in decision making. For views that require retrieval of entire or large portions of the database, the overhead can be high and special data structures may be required.

KW - "What-if' analysis

KW - Hypothetical databases

KW - Relational databases

KW - Relational views

KW - View updates

UR - http://www.scopus.com/inward/record.url?scp=30244506948&partnerID=8YFLogxK

UR - http://www.scopus.com/inward/citedby.url?scp=30244506948&partnerID=8YFLogxK

M3 - Article

VL - 9

SP - 185

EP - 203

JO - Journal of Management Information Systems

JF - Journal of Management Information Systems

SN - 0742-1222

IS - 1

ER -