Search BC Oracle Sites  Home  E-mail Us  Oracle Articles New Oracle Articles  Oracle Training  Oracle Tips  Oracle Forum  Class Catalog  Remote DBA  Oracle Tuning  Emergency 911  RAC Support  Apps Support  Analysis  Design  Implementation  Oracle Support  SQL Tuning  Security  Oracle UNIX  Oracle Linux  Monitoring  Remote support  Remote plans  Remote services  Application Server  Applications  Oracle Forms  Oracle Portal  App Upgrades  SQL Server  Oracle Concepts  Software Support  Remote Support    Development    Implementation  Consulting Staff  Consulting Prices  Help Wanted!    Oracle Posters  Oracle Books  Oracle Scripts  Ion  Excel-DB   Don Burleson Blog

Data Warehouse Platform Distribution Oracle Tips by Burleson Consulting The Data Warehouse Development Life Cycle Distributed Oracle Data Warehouses Platform Distribution (Vertical Distribution) Platform distribution refers to the existence of databases that reside on a diversity of hardware platforms (see Figure 9.2). An example would be a FoxPro system on a PC-LAN using DB2 to communicate with a mainframe. Platform distribution is often used with client/server software applications so shared databases can be distributed to PCs connected to wide area networks. Figure 9.2 Platform database distribution. Architectural Distribution Architectural distribution, shown in Figure 9.3, refers to distributed databases that involve different databases, many of which are not relational databases. Examples of architectural distribution include an object-oriented database that communicates with a relational database or a CODASYL database that communicates with a hierarchical database. Figure 9.3 Architectural database distribution. Contrary to popular opinion, architectural distribution can be the simplest form of database distribution to implement. By using the language preprocessors that come with a database, it is simple to embed commands for each of the databases in an architecture into a single program. When the program is compiled, each preprocessor is invoked, and the database calls are replaced by native calls. Using this method, a programmer can write a batch program that simultaneously communicates with a relational database and a non-relational database. For example, a JCL job stream on MVS could easily make Oracle MVS communicate with IMS. This approach is commonly used in the "master-slave" distributed database model where a master database is updated and a daily batch COBOLl program reads this database and updates several query-only databases in a different architecture. Master-slave distributed databases are discussed in more detail later in this chapter. This is an excerpt from "High Performance Data Warehousing", copyright 1997. If you like Oracle tuning, you may enjoy the book Oracle Tuning: The Definitive Reference , with over 900 pages of BC's favorite tuning tips & scripts.  You can buy it directly from the publisher and save 30%, and get instant access to the code depot of Oracle tuning scripts. ��

 

Burleson is the American Team Note: This Oracle documentation was created as a support and Oracle training reference for use by our DBA performance tuning consulting professionals.  Feel free to ask questions on our Oracle forum. Verify experience! Anyone considering using the services of an Oracle support expert should independently investigate their credentials and experience, and not rely on advertisements and self-proclaimed expertise. All legitimate Oracle experts publish their Oracle qualifications. Errata?  Oracle technology is changing and we strive to update our BC Oracle support information.  If you find an error or have a suggestion for improving our content, we would appreciate your feedback.  Just  e-mail:   and include the URL for the page.                      Burleson Consulting The Oracle of Database Support Oracle Performance Tuning Remote DBA Services   Copyright © 1996 -  2020 All rights reserved by Burleson Oracle ® is the registered trademark of Oracle Corporation.