The Database Approach
The database approach emphasizes the integration and sharing of data throughout the organization (or at least major segments of the organization). This approach requires a fundamental reorientation or shift in through process, staring with top management. Such a reorientation is difficult for most organizations; still many are making this shift today and learning that shift today and learning that information can be used as competitive weapon.
Benefits of the Database Approach
Redundancy can be reduced:
In non database systems each application has its own private files. This fact can often lead to considerable redundancy in stored data with resultant waste in storage place.
Inconsistency can be avoided:
This is really a proposition of the previous point. Suppose that a given fact about the real world - say the fact that employee E3 works in department D8 - represented by two distinct entries in the stored database. Suppose also, the DBMS is not aware of this duplication. Then the will necessarily be occasions on which the two entries will not agree - namely when one of the two has been- updated and the other has not. At such time the database is said to be inconsistent.
The data can be shared:
An individual piece of data in the database can be shared among several different users, in the sense that each of these users can have access to the same piece of data.
Standard can be enforced:
With central control of the database the DBA can ensure that all applicable standards are observed in the representation of the data. This is important when it is needed to interchange data or to do migration of data between systems.
Security restrictions can be applied:
Can define security rules to check whenever access is attempted to sensitive data. Different rules can be established for each type of access (read insert delete) to each piece of information in the database.
Integrity can be maintained:
The problem of integrity is the problem of ensuring that the data in the database is accurate. Inconsistency between two entries that are intended to represent the same fact is an example of lack of integrity. Even if there is no redundancy however the database might still contain incorrect information. For example an employee might be shown as having worked 400 hours in the week instead of 40 or as belonging to a department D9 when no such department exist. Adding integrity rules can eliminate these situations.
Data independence:
One immediate consequence of obstruction is the idea of buffering data from the process that uses data. The idea is to achieve a situation where data organization is transparent, to the users or application programs, which uses data. lf, for instance, a change is made to some part of the underlying database no application programs using affected data should need to be changed. Also if changes made to some part of an application system this should not affect the data.
The database approach emphasizes the integration and sharing of data throughout the organization (or at least major segments of the organization). This approach requires a fundamental reorientation or shift in through process, staring with top management. Such a reorientation is difficult for most organizations; still many are making this shift today and learning that shift today and learning that information can be used as competitive weapon.
Benefits of the Database Approach
Redundancy can be reduced:
In non database systems each application has its own private files. This fact can often lead to considerable redundancy in stored data with resultant waste in storage place.
Inconsistency can be avoided:
This is really a proposition of the previous point. Suppose that a given fact about the real world - say the fact that employee E3 works in department D8 - represented by two distinct entries in the stored database. Suppose also, the DBMS is not aware of this duplication. Then the will necessarily be occasions on which the two entries will not agree - namely when one of the two has been- updated and the other has not. At such time the database is said to be inconsistent.
The data can be shared:
An individual piece of data in the database can be shared among several different users, in the sense that each of these users can have access to the same piece of data.
Standard can be enforced:
With central control of the database the DBA can ensure that all applicable standards are observed in the representation of the data. This is important when it is needed to interchange data or to do migration of data between systems.
Security restrictions can be applied:
Can define security rules to check whenever access is attempted to sensitive data. Different rules can be established for each type of access (read insert delete) to each piece of information in the database.
Integrity can be maintained:
The problem of integrity is the problem of ensuring that the data in the database is accurate. Inconsistency between two entries that are intended to represent the same fact is an example of lack of integrity. Even if there is no redundancy however the database might still contain incorrect information. For example an employee might be shown as having worked 400 hours in the week instead of 40 or as belonging to a department D9 when no such department exist. Adding integrity rules can eliminate these situations.
Data independence:
One immediate consequence of obstruction is the idea of buffering data from the process that uses data. The idea is to achieve a situation where data organization is transparent, to the users or application programs, which uses data. lf, for instance, a change is made to some part of the underlying database no application programs using affected data should need to be changed. Also if changes made to some part of an application system this should not affect the data.
No comments:
Post a Comment