The Data Warehouse Lifecycle Toolkit - Kindle edition by Ralph Kimball, Margy Ross, Warren Thornthwaite, Joy Mundy, Bob Becker. Download it once and read it on your Kindle device, PC, phones or tablets. Use features like bookmarks, note taking and highlighting while reading The Data Warehouse Lifecycle Toolkit. Jun 28, 2016. The first edition of Ralph Kimball's The Data Warehouse Toolkit introduced the industry to dimensional modeling, and now his books are considered the most. It covers new and enhanced star schema dimensional modeling patterns, adds two new chapters on ETL techniques, includes new and expanded.

Oracle Technology Network is the ultimate, complete, and authoritative source of technical information and learning about Java. 阅读量：440 积分：2. 阅读量：945 积分：0.

You also agree that your personal information may be transferred and processed in the United States, and that you have read and agree to the and the. A business transaction is an interaction in the real world, usually between an enterprise and a person or another enterprise, where something is exchanged. For example, it could involve exchanging money, products, information, or service requests. Usually some bookkeeping is required to record what happened. Often this bookkeeping is done by a computer, for better scalability, reliability, and cost.

Communications between the parties involved in the business transaction is often done over a computer network, such as the Internet. This is transaction processing (TP) — the processing of business transactions by computers connected by computer networks. There are many requirements on computer-based transaction processing, such as the following. • A business transaction requires the execution of multiple operations. For example, consider the purchase of an item from an on-line catalog.

One operation records the payment and another operation records the commitment to ship the item to the customer. It is easy to imagine a simple program that would do this work. However, when scalability, reliability, and cost enter the picture, things can quickly get very complicated. • Transaction volume and database size adds complexity and undermines efficiency. We've all had the experience of being delayed because a sales person is waiting for a cash register terminal to respond or because it takes too long to download a web page.

Yet companies want to serve their customers quickly and with the least cost. • To scale up a system for high performance, transactions must execute concurrently. Uncontrolled concurrent transactions can generate wrong answers. At a rock concert, when dozens of operations are competing to reserve the same remaining seats, it's important that only one customer is assigned to each seat.

Fairness is also an issue. For example, Amazon.com spent considerable effort to ensure that when its first thousand Xboxes went on sale, each of the 50,000 customers who were vying for an Xbox had a fair chance to get one. • If a transaction runs, it must run in its entirety. In a retail sale, the item should either be exchanged for money or not sold at all. When failures occur, as they inevitably do, it's important to avoid partially completed work, such as accepting payment and not shipping the item, or vice versa. This would make the customer or the business very unhappy. • Each transaction should either return an acknowledgment that it executed or return a negative acknowledgment that it did not execute.

Those acknowledgments are important. If no acknowledgment arrives, the user doesn't know whether to resubmit a request to run the transaction again. • The system should be incrementally scalable. When a business grows, it must increase its capacity for running transactions, preferably by making an incremental purchase — not by replacing its current machine by a bigger one or, worse yet, by rebuilding the application to handle the increased workload. • When an electronic commerce (e-commerce) web site stops working, the retail enterprise is closed for business. Systems that run transactions are often ' mission critical ' to the business activity they support.

They should hardly ever be down. • Records of transactions, once completed, must be permanent and authoritative. This is often a legal requirement, as in financial transactions. Transactions must never be lost.

• The system must be able to operate well in a geographically distributed environment. Often, this implies that the system itself is distributed, with machines at multiple locations. Sometimes, this is due to a legal requirement that the system must operate in the country where the business is performed. Other times, distributed processing is used to meet technical requirements, such as efficiency, incremental scalability, and resistance to failures (using backup systems). • The system should be able to personalize each user's on-line experience based on past usage patterns. Martha Cecilia Kristine Series Ebook Login. For a retail customer, it should identify relevant discounts and advertisements and offer products customized to that user. • The system must be able to scale up predictably and inexpensively to handle Internet loads of millions of potential users.