Database administration is the management of database systems (see database management system). Database administration can be divided into four broad areas: data security, data integrity, data accessibility, and system development.
Data Security
With regard to databases, ensuring data security includes the assignment and control of users’ level of access to sensi-tive data and the use of monitoring tools to detect compro-mise, diversion, or unauthorized changes to database files (see data security). When data is proprietary, licensing agreements with both database vendors and content provid-ers may also need to be enforced.
Data Integrity
Data integrity is related to data security, since the com-pleteness and accuracy of data that has been compromised can no longer be guaranteed. However, data integrity also requires the development and testing of procedures for the entry and verification of data (input) as well as verifying the accuracy of reports (output). Database administrators may do some programming, but generally work with the programming staff in maintaining data integrity. Since most data in computers ultimately comes from human beings, the training of operators is also important.
Within the database structure itself, the links between data fields must be maintained (referential integrity) and a locking system must be employed to ensure that a new update is not processed while a pending one is incomplete (see transaction processing).
Internal procedures and external regulations may require that a database be periodically audited for accuracy. While this may be the province of a specially trained infor-mation processing auditor, it is often added to the duties of the database administrator. (See also auditing in data processing.)
Data Accessibility
Accessibility has two aspects. First, the system must be reli-able. Data must be available whenever needed by the orga-nization, and in many applications such as e-commerce, this means 24 hours a day, 7 days a week (24/7). Reliability requires making the system as robust as possible, such as by “mirroring” the database on multiple servers (which in turn requires making sure updates are stored concurrently). Failure must also be planned for, which means the imple- mentation of onsite and offsite backups and procedures for restoring data (see backup and archive systems).
Data Security
With regard to databases, ensuring data security includes the assignment and control of users’ level of access to sensi-tive data and the use of monitoring tools to detect compro-mise, diversion, or unauthorized changes to database files (see data security). When data is proprietary, licensing agreements with both database vendors and content provid-ers may also need to be enforced.
Data Integrity
Data integrity is related to data security, since the com-pleteness and accuracy of data that has been compromised can no longer be guaranteed. However, data integrity also requires the development and testing of procedures for the entry and verification of data (input) as well as verifying the accuracy of reports (output). Database administrators may do some programming, but generally work with the programming staff in maintaining data integrity. Since most data in computers ultimately comes from human beings, the training of operators is also important.
Within the database structure itself, the links between data fields must be maintained (referential integrity) and a locking system must be employed to ensure that a new update is not processed while a pending one is incomplete (see transaction processing).
Internal procedures and external regulations may require that a database be periodically audited for accuracy. While this may be the province of a specially trained infor-mation processing auditor, it is often added to the duties of the database administrator. (See also auditing in data processing.)
Data Accessibility
Accessibility has two aspects. First, the system must be reli-able. Data must be available whenever needed by the orga-nization, and in many applications such as e-commerce, this means 24 hours a day, 7 days a week (24/7). Reliability requires making the system as robust as possible, such as by “mirroring” the database on multiple servers (which in turn requires making sure updates are stored concurrently). Failure must also be planned for, which means the imple- mentation of onsite and offsite backups and procedures for restoring data (see backup and archive systems).
No comments:
Post a Comment