Laserfiche WebLink
<br />e <br /> <br />e <br /> <br />~e <br /> <br />003H2 <br /> <br />few combinations of centralized/distributed data processing. <br /> <br />When processing centrally, a single machine or set of machines (e,g, a single <br />database server) is used to store data and process requests to fetch and modify <br />this data (Figure 2), The main advantage of this approach is that there is only <br />one copy of the data (i.e. there is no data duplication); thus, there is a high <br />probability of maintaining data integrity. The main disadvantage of this <br />approach is that all requests for data come to the database server therefore <br />creating the possibility of a bottle-neck in processing the requests. <br /> <br />The centralized data/centralized processing concerns a configuration used <br />predominantly during the 1960's and 1970's (e.g, time sharing and .batch <br />processing). <br /> <br />There are several commercially available database management systems that <br />support centralized data management and processing <br /> <br />The option of distributed processing allows data to be stored and processed on <br />many machines (possibly over a wide area). Neither the users nor the <br />application programs have to be aware of where the data is physically stored. <br /> <br />Data in a distributed database (Figure 3) can be distributed with or without <br />duplication. An advantage of distribution with data duplication is that if one of <br />the database servers is down, back-up copies of the data on other servers exist. <br />However, this could lead to the risk of data being accessed that is out of date. <br />This problem can be addressed by having management protocols in place that <br />assure a high probability of distributing updates to the database at reasonable <br />time increments, An advantage of distribution without data duplication is less <br />storage and greater data integrity. However. if one of the servers goes down, <br />some of the data will not be accessible, <br /> <br />There are a few commercially available database management systems that <br />support distributed databases without data duplication, There are no <br />geographic information systems that support distributed data. <br /> <br />Data exchange is an important pan of the system configuration since there is a <br />clear need for users from remote sites to have access to data and programs. <br />There are a number of options for moving data/programs between users: media <br />transfer, batch file. and interactive data communications. <br /> <br />Media transfer involves physical media such as tapes and diskettes. Data and! <br />or programs are copied onto the physical media, The physical media are then <br />physically moved (e.g, via US Mail. etc.) to location(s) where they are needed, <br />At those sites data and programs are then copied onto the local machine(s); <br />thus, there is duplication of data. Data being moved on the physical media <br />must be in a format that the destination machine can interpreI (e.g, ASCII). The <br />obvious problem with this method is that moving data from one machine to <br />another can be a slow process(e,g, a minimum turn around time of a few hours <br />to several days). <br /> <br />Centralized <br />Processing <br /> <br />Distributed <br />Processing <br /> <br />Data Exchange <br /> <br />I <br />I <br />I I <br />I <br />I <br />, <br /> <br />DAMES& MOORE/CA DSWES -25 <br />