database administration

© Michael Lang, National University of Ireland, Galway1

Database Administrati

on


Database Administration

• Database Management Systems facilitate Interpretation and presentation of data

Distribution of data and information

Data preservation and monitoring

Control over data duplication and use

• Supports managerial decision making Top (Strategic / Long-term)

Middle (Tactical / Medium-term)

Operational (Routine / Short-term day-to-day)


Data-Information-Decision Cycle



“Bad administration, to be sure, can destroy good policy; but good administration can never save bad policy”

– Adlai Stevenson, 1952

• Modern emphasis on responsible and ethical “corporate governance” and “IT governance”

Focus on accountability, transparency, economic efficiency, responsiveness to stakeholders, effective stewardship

• A disorganised information system is like an attic full of junk … you can’t remember where things are, or indeed what things are in there at all !

The essential role of the Database Administrator is to keep things neatly ordered, organised in such a way that data can be quickly and easily retrieved, while at the same time maintaining control over what is stored and who has privileges to see what

Simply put, the Database Administrator is both a caretaker and a gatekeeper


Compliancee.g. Data Security, Privacy, Sarbanes-Oxley

Quality Costs

Expanded Uses

Increased Volumes

Database Security

Data Quality

Data Archiving

Data Extraction

Metadata Management

Driving FactorsAspects of Database Administration

Data / Database Administration


Evolution of Database Administration

• Roots of Database Administration are in decentralised file systems 1960s / 1970s: “Electronic Data Processing” (EDP) or ”Data

Processing” (DP) Department

1980s / 1990s: Information systems (IS) department

• The historical model of growth displayed by many organisations starts out with separate business units independently constructing their own systems (“islands of information”), until eventually over time a critical mass breaking point is reached:

Nothing fits together ! The data is not integrated

How do we begin to integrate these legacy systems ?

Need for “reverse engineering”, good maintenance documentation, metadata

… enter the Database Administrator


Evolution of Database Administration

• Database administration created to handle complex data management tasks

• Database Administrator (DBA) is responsible for control of database

• Factors affecting placement of DBA function in an organisation Organisational structure e.g. matrix, hierarchy, or autonomous

consultative function

Size and complexity of operations

Geographic distribution of facilities

• General coordinator of all DBAs might be called the “Systems Administrator”

• Generally, Database Administrator (DBA) also fulfills role of Data Administrator (DA)

These labels are an artificial separation as roles are intrinsically linked

• Head of Information Systems is the “Chief Information Officer” (CIO)


Data Administration -v- Database Administration



• Backup/Recovery• Disaster Recovery• Reorganisation• Performance Monitoring• Application Call Level Tuning• Data Structure Tuning• Capacity Planning

Managing the database environment

Managing the content and uses of data

Data Administration

• Database Security• Data Privacy Protection• Data Quality Improvement• Data Quality Monitoring• Database Archiving• Data Extraction• Metadata Management

Data Administration -v- Database Administration


DBA Skills


DBA Activities and Services


DBA Services: End-User Support

• User requirements gathering

• Conflict and problem resolution

• Finding solutions to information needs

• Ensuring quality and integrity of applications and data

• Building end-user confidence

• Managing the training and support of DBMS users


• Policies General statements of direction or action

Communicate and support DBA goals

• Standards More detailed and specific than policies

Describe minimum requirement of DBA activity

• Procedures Written instructions that describe steps for activity

Support and enhance work environment

DBA Services: Policies, Procedures, & Standards


• Authorisation management User access management

View definition

DBMS utilities access control

DBMS usage monitoring

• Security breaches Preserved integrity

• Data recovery may not be necessary Corrupted integrity

• Database must be recovered

DBA Services: Security, Privacy, & Integrity


• Database Security Officer (DSO)

• Disaster management Periodic data and applications backups

Proper backup identification

Convenient and safe backup storage

Physical protection

Personal access control

Insurance coverage for the data in the database

• Data recovery and contingency plans must be tested and evaluated

• Backup and recovery may not cover all aspects of IS

DBA Services: Data Backup and Recovery


• Data useful in right hands at right time

• Current philosophy makes authorised data access easier

• Sophisticated query tools

• Web front ends

• Data democracy

• Cautions due to improper use of data

DBA Services: Data Distribution and Use


• Evaluation, selection, and installation of DBMS and related utilities

• Design and implementation of databases and applications

• Testing and evaluation of databases and applications

• Operation of the DBMS, utilities, and applications

• Training and supporting users

• Maintenance of the DBMS, utilities, and applications

DBA’s Technical Role


Selection of Hardware & Software

• How many users will simultaneously access the database?

• Will the database need to be geographically distributed?

• What is the maximum size of the database?

• How many transactions per second can the DBMS handle?

• What kind of support for on-line transaction processing is available?

• What are the initial and ongoing costs of using the product?

• What is the extent of training required, will it be provided, and what are the associated costs?


• Information Engineering (IE) translates strategic goals of the company into data and applications

• Focuses on description of corporate data instead of the processes

• Output is Information Systems Architecture (ISA) Serves as the basis for planning, development, and

control of future IS

Data Administration Strategy: Information

Engineering


• IE originated separately in Australia (Finkelstein), England (Palmer), and USA (Martin)

Hence, there are many closely related derivatives of “IE”

• Underlying assumptions of IE: Data is considered as being at the heart of an information system, and the

enterprise data model plays a central role in the information strategy of a business

Data is assumed to be much more stable than the processes and procedures that act upon it – processes change in response to individual needs and the business environment, but the data model only changes when the meaning and relevance of data changes

Methodologies that are process-centric are more likely to fail due to constantly shifting requirements

However, even though IE is data-centric, it recognises that processes have to be considered in detail

Information Engineering


• IE is a data-driven but process-sensitive methodology that is applied to the organisation as a whole rather than on an ad-hoc project-by-project basis

Information Engineering (IE)


• IE is a top-down methodology

• Phases: Information Strategy

Planning

Business Area Analysis

Business Systems Design

Technical Design, Construction & Cutover

Information Engineering


Further Reading• Rob & Coronel (2007) Database Systems, Chapter 15:


• See Recommended Readings on http://apollo.nuigalway.ie under course Web page for MS885.ii

database administration

Documents