NIH Enterprise Architecture Home

Data Warehouse (DW) Database Server Brick

Description

Data Warehouse (DW) database functional requirements are different than Online Transaction Processing (OLTP) Database Management Sytems (DBMS) in that they support large databases, complex multi-table join processing and schema support, and have specialized index technology, workload management, and data partitioning capabilities. Most importantly, they support parallel capabilities (e.g., I/O, query and operations), and parallel utilities (e.g., backup/recovery and reorganization). DW databases are generally not updated real time, but are frequently updated via over night, batch oriented processes. 

Brick Information

Tactical

(0-2 years)

Strategic

(2-5 years)

  • IBM DB2 Universal Database
  • Microsoft SQL Server
  • MySQL
  • Oracle
  • IBM DB2 Universal Database
  • Microsoft SQL Server
  • Oracle

Retirement

(To be eliminated)

Containment

(No new development)

 

  • Microsoft Access

Baseline

(Today)

Emerging

(To track)

  • IBM DB2 Universal Database
  • Microsoft Access
  • Microsoft SQL Server
  • MySQL
  • Oracle
  • Evolving open source productsComments

Comments

  • The products designated for use are intended for applications running on server class machines. Smaller, locally used applications designed to support no more than 10 users are not covered by these specifications.
  • Evolving open source products are Emerging because open source developers have done a better job of modularizing their software, making it move feasible to combine components in order to produce a desired solution.
  • Oracle and Microsoft SQL Server are Tactical/Strategic for the current and previous releases and only when running on any of the operating systems/platforms designated as Tactical or Strategic in Server Platform Brick.
  • IBM DB2 Universal Database is Tactical/Strategic when run on IBM-OS/390-zOS or AIX.
  • MySQL is designated as Tactical because, although it is not as functional and scalable as the databases listed as Tactical and Strategic, it is open source and quickly gaining in usage.
  • Microsoft Access is designated Containment because is not as functional and scalable as the databases listed as Tactical and Strategic.
  • Tactical and strategic products were selected to leverage NIH's investment in products that are a proven fit for NIH's known future needs. Leveraging baseline products in the future will minimize the operations, maintenance, support and training costs of new products.
  • Some baseline products have been designated retirement and containment. These products are either not as widely or successfully deployed at NIH, or they do not provide as much functionality, value, or Total Cost of Ownership as the selected tactical and strategic products.

Time Table

This architecture definition approved on: May 25, 2005

The next review is scheduled in: TBD