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

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

Research output: Contribution to journalArticle

3 Scopus citations

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
DOIs
StatePublished - Jan 1 1992

Keywords

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

ASJC Scopus subject areas

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

Fingerprint Dive into the research topics of 'Performance Analysis of "What-If" Databases Using Independently Updated Views'. Together they form a unique fingerprint.

  • Cite this