Fundamentals of Database Design

Design Methodologies

Fundamentals of Database

Often as a company grows there may be a demand , because their data volumes increases and it is difficult to store their data physically in papers .They needed effective secure, and easy ways to do this. To counteract this companies came up with file systems which had their own constraints .So they went for the latest used solution now available the database. Temenos a technology manager cited about a relational database oracle as below

"Oracle Database Appliance as an ideal 'Bank-in-a-Box' solution for T24 customers who are looking for reduced deployment costs and low maintenance with high performance. We are excited with the Oracle Database Appliance's new virtualized platform that will provide workload isolation between the database and application."

(Temenos,n.d)

Fundamentals of a database are people, hardware, software, DBMS

People:

For a growing company databases have to be created, maintained and supported. To achieve this skilled people on database side are needed. Also there are other day to day tasks in administration for Database people.

Hardware:

Essential Hardware components are needed for the installation of the database software. It might be on a Mainframe system with specific Ram , Speed or Disc space. These hardware

requirements are provided on the installation manual that comes with the software or in a document.

Software:

software is needed to install the database in a computer. They can either be installed from a compact disc, network or downloaded .For example the Db2 software is mostly installed and used in a Mainframe environment. There are installation engineers or system programmers who configure the software and make the environment available and r...

... middle of paper ...

...accommodate further processing requirements. Also reduces the number of data dependencies that should be analyzed, using the extended ER model conceptualization, and maintains data integrity through normalization. This approach can be implemented manually or in a simple software package as long as a "good" solution is acceptable and absolute optimality is not required.

Normalisation reduces data redundancy and integrity. It can be a good technique to better organisation of data. But it has pros and cons on the other hand. Usually companies don’t go beyond the third normal form as it increases the complexity more. Also it reduces the speed as more joins have to be made to join all the split tables due to normalisation technique. It all mostly depends on the volume of data, complexity of business processes and rules to determine the normalisation level a company needs