Open Framework, Information Management Strategy & Collaborative Governance | Data & Social Methodology - MIKE2.0 Methodology
Wiki Home
Collapse Expand Close

Collapse Expand Close

To join, please contact us.

Improve MIKE 2.0
Collapse Expand Close
Need somewhere to start? How about the most wanted pages; or the pages we know need more work; or even the stub that somebody else has started, but hasn't been able to finish. Or create a ticket for any issues you have found.

Physical Database Design Deliverable Template

From MIKE2.0 Methodology

Jump to: navigation, search
Under construction.png
This article is currently Under Construction. It is undergoing major changes as it is in the early stages of development. Users should help contribute to this article to get it to the point where is ready for a Peer Review.
This deliverable template is used to describe a sample of the MIKE2.0 Methodology (typically at a task level). More templates are now being added to MIKE2.0 as this has been a frequently requested aspect of the methodology. Contributors are strongly encouraged to assist in this effort.
Deliverable templates are illustrative as opposed to fully representative. Please help add examples to this template that are representative of the proposed output.


Whereas the Physical Database Design covers aspects of the database design that are primarily related to modelling, there are other design aspects that may need to be give to the Database Administrators. Some common steps for which a process should be designed include:

Table Maintenance

The DBA must manage the creation and archiving of the tables in the information system. Periodically, the DBA will need to create the next period’s partition tables and archive the oldest set of tables (assuming that data partitioning strategies are being used). Using a separate set of tables for each time period simplifies the process by reducing the number of tables involved and allowing the system to "age out" the oldest data.

Database Expansions and Rebuilds

Database Expansion and Rebuilds deal with standard space management issues within databases such as:

  • Space allocation - data file and tablespace allocation
  • Data file placement and configuration
  • Import and exports for performance reasons, i.e., defragmentation
  • Index rebuilds
  • Much of this information is technical metadata that should be updated into the physical data model as part of a metadata-driven approach.

Example of a Physical Database Design

Wiki Contributors
Collapse Expand Close