Case Study Database Design

Case Study Database Design-40
Each case study begins with a real world scenario and takes the user through the E-R and R-M diagrams, ending with executable SQL commands to implement the derived designs.: The owners of a small computer repair shop would like to keep track of the repair jobs for computers they repair, the items used for each repair job, the labor costs for each repair job, the repairmen performing each repair job, and the total cost of each repair job.When customers bring their computers in to be repaired, they make a deposit on the repair job and are given a date to return and uplift their computer.

The financial measures that analysts track are profit and loss and inventory.

TBC uses spreadsheet packages to prepare budget data and perform variance reporting.

Because TBC plans and tracks a variety of products over several markets, the process of deriving and analyzing data is tedious.

Last month, analysts spent most of their time entering and rekeying data and preparing reports.

With Essbase, you can use as many dimensions as you need for analysis.

A typical Essbase database contains at least seven standard dimensions (nonattribute dimensions) and many more attribute dimensions.

Users can access the server and load data from various sources and retrieve data as needed.

TBC has a variety of users, so TBC expects that different users will have different security levels for accessing data.

A detailed plan that outlines data sources, user needs, and prospective database elements can save you development and implementation time.

The planning and analysis phase involves these tasks: First, evaluate the source data to be included in the database.


Comments Case Study Database Design

The Latest from ©