Heuristics for selecting robust database structures with dynamic query patterns

Andrew N.K. Chen, Paulo B. Goes, Alok Gupta, James R. Marsden

Research output: Contribution to journalArticlepeer-review

8 Scopus citations

Abstract

The success of a company increasingly depends on timely information (internal or external) being available to the right person at the right time for crucial managerial decision-making. Achieving such a "right time/right place" duet depends directly on database performance. A database system has been a core component that supports modern business system such as enterprise resource planning (ERP) system that integrates and supports all enterprise processes including product designing and engineering, manufacturing, and other business functions to achieve highest efficiency and effectiveness of operations. We develop and demonstrate through a proof-of-concept case study, a new "query-driven" heuristics for database design that seeks to identify database structures that perform robustly in dynamic settings with dynamic queries. Our focus is the design of efficient structures to process read-only queries in complex environments. Our heuristics begins with detailed analysis of relationships between diverse queries and the performance of different database structures. These relationships are then used in a series of steps that identify "robust" database structures that maintain high performance levels for a wide range of query patterns. We conjecture that our heuristics can facilitate efficient operations and effective decision-making of companies in today's dynamic environment.

Original languageEnglish (US)
Pages (from-to)200-220
Number of pages21
JournalEuropean Journal of Operational Research
Volume168
Issue number1
DOIs
StatePublished - Jan 1 2006

Keywords

  • Computing science
  • Database management
  • Heuristics
  • Simulation

Fingerprint

Dive into the research topics of 'Heuristics for selecting robust database structures with dynamic query patterns'. Together they form a unique fingerprint.

Cite this