Distributed Database Essay Example | Topics and Well Written Essays - 3000 words

Distributed Database - Essay ExampleBest customers are those who subscribe to 7day, 52week, EZPay automatic payment from trust card subscriptions.2. Existance in the marketplace and we have touched them. By building complete universe of households with extended demographics, and by attaching touch or contact histories to individuals, tramp determine what is working on what types of customers (and what isnt working). We need to build touch history over time. Value increase as more history is accumulated.3. We build a loyalty gravel based on a subscribers payment history. Loyalty can be defined as overall duration as subscriber, subjugate of consecutive payments (with unbroken service), etc. We can then create a profile of a loyal subscriber and more effectively identify believably churners vs. likely loyal subscribers.This is a very important step in the info warehousing project, as the foundation of the data warehousing system is the data model. A good data model will allow th e data warehousing system to grow easily, as well as allowing for good performance. In data warehousing project, the logical data model is built based on user requirements, and then it is translated into the physical data model. This project uses Dimensional modeling, which is the denomination of the logical design technique often used for data warehouses. It is different from entity-relationship modeling.Entity relationship modeling is a logical design technique that seeks to eliminate data redundancy while Dimensional modeling seeks to present data in a standard framework that is intuitive and allows for high-performance access. Every dimensional model is composed of one table with a multi part key, called the fact table, and a set of smaller tables called dimensional tables. Each dimension table has a individual part primary key that corresponds exactly to one of the components of the multi part key in the fact table. This characteristic star like structure is often called a st ar join. A fact table, because it has a multi part key made up of two or more foreign keys always expresses a many-to-many relationship. The