Logical design data Warehouse
A logical design is conceptual and abstract. You do not deal with the physical implementation details yet. You deal only with defining the types of information that you need.
One technique you can use to model your organization's logical information requirements is entity-relationship modeling. Entity-relationship modeling involves identifying the things of importance (entities), the properties of these things (attributes), and how they are related to one another (relationships).
The process of logical design involves arranging data into a series of logical relationships called entities and attributes. An entity represents a chunk of information. In relational databases, an entity often maps to a table. An attribute is a component of an entity that helps define the uniqueness of the entity. In relational databases, an attribute maps to a column.
To ensure that your data is consistent, you must use unique identifiers. A unique identifier is something you add to tables so that you can differentiate between the same item when it appears in different places. In a physical design, this is usually a primary key.
Entity-relationship modeling is purely logical and applies to both OLTP and data warehousing systems. It is also applicable to the various common physical schema modeling techniques found in data warehousing environments, namely normalized (3NF) schemas in Enterprise Data Warehousing environments, star or snowflake schemas in data marts, or hybrid schemas with components of both of these classical modeling techniques.
What is a Schema?
A schema is a collection of database objects, including tables, views, indexes, and synonyms. You can arrange schema objects in the schema models designed for data warehousing in a variety of ways. Most data warehouses use a dimensional model.
The model of your source data and the requirements of your users help you design the data warehouse schema. You can sometimes get the source model from your company's enterprise data model and reverse-engineer the logical data model for the data warehouse from this. The physical implementation of the logical data warehouse model may require some changes to adapt it to your system parameters—size of computer, number of users, storage capacity, type of network, and software. A key part of designing the schema is whether to use a third normal form, star, or snowflake schema, and these are discussed later.
You might also like
Cardiac Surgery in the Adult, Fourth Edition
Book (McGraw-Hill Professional)
Survey: IT and business at odds on defining big data success — TechTarget
Data warehouse vendors will feel the burn. Hadoop and NoSQL products probably won't replace the enterprise data warehouse, but they are competing for workloads.
Leviton 51120-3R 120/240 Volt Panel Protector 4-Mode Protection, Light Commercial/Residential Grade, In NEMA 3R Enclosure
Home Improvement (Leviton)
WD Red 3 TB NAS Hard Drive: 3.5 Inch, SATA III, 64 MB Cache - WD30EFRX
Personal Computer (Western Digital)
Root Cause Analysis: Improving Performance for Bottom-Line Results, Fourth Edition
Book (CRC Press)
Omron 10 Plus Series Upper Arm Blood Pressure Monitor with ComFit Cuff
Health and Beauty (Omron)