(Continued from previous part...)

Database Administrator:

Duties

Security
Security means that users’ ability to access and change data conforms to the policies of the business and the delegation decisions of its managers. Like other metadata, a relational DBMS manages security information in the form of tables. These tables are the “keys to the kingdom” and so it is important to protect them from intruders.

Availability
Availability means that authorized users can access and change data as needed to support the business. Increasingly, businesses are coming to expect their data to be available at all times (“7x24”, or seven days a week, 24 hours a day). The IT industry has responded to the availability challenge with hardware and network redundancy and increasing online administrative capabilities.

Performance
Performance means that the database does not cause unreasonable online response times, and it does not cause unattended programs to run for an unworkable period of time. In complex client/server and three-tier systems, the database is just one of many elements that determine the performance that online users and unattended programs experience. Performance is a major motivation for the DBA to become a generalist and coordinate with specialists in other parts of the system outside of traditional bureaucratic reporting lines.
Techniques for database performance tuning have changed as DBA's have become more sophisticated in their understanding of what causes performance problems and their ability to diagnose the problem.
In the 1990's, DBA's often focused on the database as a whole, and looked at database-wide statistics for clues that might help them find out why the system was slow. Also, the actions DBA's took in their attempts to solve performance problems were often at the global, database level, such as changing the amount of computer memory available to the database, or changing the amount of memory available to any database program that needed to sort data.
Around the year 2000, many of the most fundamental assumptions about database performance tuning were discovered to be myths. Most famously, the database buffer cache hit ratio, once thought to be the most reliable way to measure database performance, was found to be a completely meaningless statistic.
As of 2005, the fog has lifted. DBA's understand that performance problems initially must be diagnosed, and this is best done by examining individual SQL programs, not the database as a whole. Various tools, some included with the database and some available from third parties, provide a behind the scenes look at how the database is handling the SQL program, shedding light on what's taking so long. Oracle's EXPLAIN PLAN utility is somewhat helpful, but Oracle's TKPROF provides a more complete diagnostic report. Every site that licenses Oracle has these utilities, since they are provided along with Oracle's database software.
Having identified the problem, the individual SQL statement can be tuned, and this is usually done by either rewriting it, using hints, adding or modifying indexes, or sometimes modifying the database tables themselves.

Development/Testing Support
Development and testing support is typically what the database administrator regards as his or her least important duty, while results-oriented managers consider it the DBA’s most important duty. Support activities include collecting sample production data for testing new and changed programs and loading it into test databases; consulting with programmers about performance tuning; and making table design changes to provide new kinds of storage for new program functions.
Here are some IT roles that are related to the role of database administrator:
* Application programmer
* System administrator
* Data administrator
* Data architect

(Continued on next part...)