The DBA

ADMINISTRACION
DE
BASE DE DATOS
System Concepts
Database Administration: The Complete Guide to Practices and Procedures15.1 ©Silberschatz, KorthCraig
and Sudarshan
S. Mullins
What Is a DBA?
Every organization using a database management system

(DBMS) to manage data requires a database administration
group to ensure the effective use and deployment of the
company's databases.
Since most modern organizations of any size use a DBMS, the
need for a database administrator (DBA) is greater today than
ever before. However, the discipline of database administration
is neither well understood nor universally practiced in a coherent
and easily replicated manner.
System Concepts
Database Administration: The Complete Guide to Practices and 15.2 ©Silberschatz, KorthCraig
and Sudarshan
S. Mullins
What Is a DBA?
DBMS software is so complex these days that very few people

understand more than just the basics (like SQL). However, DBAs
understand the complexities of the DBMS, making them a
valuable resource. Indeed, sometimes the only source of
database management and development knowledge within the
organization is the DBA.
DBAs need to acquire exceptional communication skills. DBAs
frequently interface with many different types of people:
technicians, programmers, end users, customers, and
executives.
A DBA is the information technician responsible for ensuring the
ongoing operational functionality and efficiency of an
organization's databases and the applications that access those
databases.
Database System Concepts 15.3 ©Silberschatz, Korth and Sudarshan

Why Learn Database Administration?
Data is at the center of today's applications; today's

organizations simply cannot operate without data. In many ways,
business today is data. Without data, businesses would not have
the ability to manage finances, conduct transactions, or contact
their customers. Databases are created to store and organize
this data. The better the design and utility of the database, the
better the organization will be positioned to compete for
business.

What is a Database and DBMS?
A database is an organized store of data wherein the data is

accessible by named data elements (for example, fields, records,
and files). And what is a database management system?
A DBMS is software that enables end users or application

programmers to share and manage data. It provides a
systematic method of creating, updating, retrieving, and storing
in formation in a database.
A DBMS is also generally responsible for data integrity, data

security, data access control and optimization, automated
rollback, restart, and recovery

Relationship of DBMS to database

What Is a DBA?
In addition to database management fundamentals, DBAs must

be experts in the specific DBMS in use, and there may be many
in the organization. For example, a large organization might use
DB2 on the mainframe, Oracle and Informix on several different
UNIX platforms, and SQL Server on Windows
The DBA group, therefore, must have expertise in each of these

different management systems and platforms. Furthermore, the
DBA must be capable of determining which DBMS and platform
is best suited to the needs of each application.
The DBA group must be able to act impartially and implement

decisions based on the best fit of application, DBMS, and
platform.

The Management Discipline of Database
Administration
Database administration is rarely approached as a management
discipline.
The reactive DBA functions more like a the proactive DBA implements practices
firefighter than an administrator; he and procedures to avoid problems before
attempts to resolve problems only after they occur. A proactive database
problems occur. The reactive DBA is administrator develops and implements a
focused on resolving the biggest problem strategic blueprint for deploying databases
confronting him within the organization
This plan should address all phases of the

application development life cycle. A data
specialist, usually the DBA, should be
involved during each phase of the cycle,

The application development life cycle
must be available to identify the data
components of the project
the rudimentary data requirements must be

transformed into a conceptual and logical
data model
the logical data model must be
translated to a physical database
design that can be implemented
the DBA must develop and using a DBMS
implement a process to refresh
the DBA becomes
test data to enable repeatable
engaged in the entire
test runs
process once again,
from requirements
DBA ensures that the DBMS is prepared gathering to
for the new workload implementation.
the DBA performs a host of duties including

assuring availability, performance
monitoring, tuning, backup and recovery,
and authorization management
Administration
Finally, when the application reaches the end of its useful life, the DBA must
help to determine the final status of the data used by the application:
• Is the data no longer required, or do other applications and processes use

the data, too?
•Are there regulations that require the data to be stored longer than the life
of the application?
•Does the business have any privacy policies that impose special rules for
handling the data?

Administration
Finally, when the application reaches the end of its useful life, the DBA must
help to determine the final status of the data used by the application:
• Is the data no longer required, or do other applications and processes use

the data, too?
•Are there regulations that require the data to be stored longer than the life
of the application?
•Does the business have any privacy policies that impose special rules for
handling the data?

A Day in the Life of a DBA
Based on the article and the above reviewed,

please develop the next questions:
A Day in the Life of a DBA
A day in the life of a DBA is usually quite hectic. The DBA maintains
production and test environments, monitors active application development
projects, attends strategy and design meetings, selects and evaluates new
1.- What is a DBA?
products, and connects legacy systems to the Web. And, of course: Joe in
Accounting, he just resubmitted that query from hell that's bringing the 2.- Why an enterprise requiere DBA and when
system to a halt. Can you do something about that? All of this can occur
within a single workday. not
To add to the chaos, DBAs are expected to know everything about
everything. From technical and business jargon to the latest management
3.- When use a team of DBAs?
and technology fads, the DBA is expected to be "in the know." And do not
expect any private time: A DBA must be prepared for interruptions at any
time to answer any type of question—and not just about databases, either.
4.- What are the duties of a DBA
When application problems occur, the database environment is frequently
5.- What are the main skills of a DBA
the first thing blamed. The database is "guilty until proven innocent." A DBA
is rarely approached with a question like "I've got some really bad SQL 6.- And what other alternative skills
here. Can you help me fix it?" Instead, the DBA is forced to investigate
problems where the underlying assumption is that the DBMS or perhaps
the DBA is at fault, hen the most common cause of relational performance
7.- Why DBA is a non-stop work
problems is inefficiently coded applications.
8.- What does mean: The database is "guilty until
Oftentimes the DBA is forced to prove that the database is not the source
of the problem. The DBA must know enough about all aspects of IT to track
down errors and exonerate the DBMS and database structures he has
proven innocent”
designed. So he must be an expert in database technology, but also have
semi-expert knowledge of the IT components with which the DBMS 9.- How do you think is a typical day for an
interacts: application programming languages, operating systems, network
protocols and products, transaction processors, every type of computer
hardware imaginable, and more. The need to understand such diverse
Ecuadorian DBA?
elements makes the DBA a very valuable resource. It also makes the job
interesting and challenging.
10.- In what phase of applications development
lifecycle, do you believe have more impact the
DBA? Why?

Database, Data, and System Administration
Many organizations combine data administration into the database

administration role.
Data Administration
•Data administration separates the business aspects of data resource management

from the technology used to manage data
•The data administrator (DA) is responsible for understanding the business lexicon
and translating it into a logical data model
•The DA would be involved more in the requirements gathering, analysis, and design
phase, the DBA in the design, development, testing, and operational phases

Data Administration
Another difference between a DA and a DBA is the focus of effort. The DA

is responsible for the following tasks:
• Identifying and cataloging the data required by business users
• Producing conceptual and logical data models to accurately depict

the relationship among data elements for business processes
• Creating an enterprise data model that incorporates all of the data

used by all of the organization's business processes
• Setting data policies for the organization
• Identifying data owners and data administrators
• Setting standards for control and usage of data

Data Administration
•Furthermore, the DA deals with metadata, as opposed to the DBA, who

deals with data.
•Metadata is often described as data about data; more accurately,

metadata is the description of the data and data interfaces required by the
business.
•Data administration is responsible for the business's metadata strategy.
•Examples of metadata include the definition of business names for a data

element, any abbreviations used for that element, and the data type and
length of the element. Data without metadata is difficult to use.
•Metadata provides the context by which data can be understood.

Data Administration
Unfortunately, the DBA will usually not be able to assume all of the
functions and responsibility of a DA as summarized in this section for a
number of reasons:
•The DBA has many other technical duties to perform that will
consume most of his time.
•The manager of the DBA group typically does not have an executive
position enabling him to dictate policy.
•The DBA generally does not have the skills to communicate

effectively with business users and build consensus.

Database Administration

System Administration
•The SA is responsible for the installation and setup of the DBMS. The SA
typically has no responsibility for database design and support. Instead,
the DBA is responsible for the databases and the SA is responsible for
DBMS installation, modification, and support.
•The SA ensures that the IT infrastructure is implemented such that the

DBMS is configured to work with other enabling system software.
•The SA may need to work with other technicians to configure transaction

processors, message queueing software, networking protocols, and
operating system parameters to enable the DBMS to operate effectively

DA, DBA, and SA responsibilities

DBA Tasks
Ensuring that an organization's data and databases are useful, usable,
available, and correct requires the DBA to perform a variety of tasks in a
variety of areas.
Database Design
The DBA must be able to transform a logical data model into a physical
database implementation. The DBA must ensure that the database design
and implementation will enable a useful database for the applications and
clients that will use it.

DBA Tasks
Performance Monitoring and Tuning
Five factors influence database performance: workload, throughput,
resources, optimization, and contention.
•The workload is a combination of online transactions, batch jobs, ad
hoc queries, data warehousing, analytical queries, and commands
directed through the system at any given time.
•Throughput defines the overall capability of the computer hardware

and software to process data.
•The hardware and software tools at the disposal of the system are
known as the resources of the system.
•Optimization refers to the analysis of database requests with query

cost formulas to generate efficient access paths to data.
•Contention is the condition in which two or more components

of the workload are attempting to use a single resource in a
conflicting way

DBA Tasks
Performance Monitoring and Tuning

DBA Tasks
Availability
The first component of availability is keeping the DBMS up and running.

Vigilant monitoring and automated alerts can be used to warn of DBMS
outages and the need for corrective action.
An additional component of availability is minimizing the amount of

downtime required to perform administrative tasks.
The DBA must understand all of these aspects of availability and

ensure that each application is receiving the correct level of
availability for its needs.

DBA Tasks
Database Security and Authorization
It is the responsibility of the DBA to ensure that data is available only to

authorized users. Security must be administered for many actions required
by the database environment:
• Creating database objects, including databases, tables, views, and program structures
• Altering the structure of database objects
• Accessing the system catalog
• Reading and modifying data in tables
• Creating and accessing user-defined functions and data types
• Running stored procedures
• Starting and stopping databases and associated database objects
• Setting and modifying DBMS parameters and specifications
• Running database utilities such as LOAD, RECOVER, and REORG

DBA Tasks
Backup and Recovery
The DBA must be prepared to recover data to a usable point, no matter what
the cause, and to do so as quickly as possible.
To be prepared for any type of recovery, the DBA needs to develop a

backup strategy to ensure that data is not lost in the event of an error in
software, hardware, or a manual process.

DBA Tasks
Data Integrity
A database must be designed to store the correct data in the correct way
without that data becoming damaged or corrupted.
The DBA implements integrity rules using features of the DBMS.
Three aspects of integrity are relevant to our discussion of databases:

physical, semantic, and internal

DBA Tasks
DBMS Release Migration
The DBA is also responsible for managing the migration from release to
release of the DBMS.
Jack-of-All-Trades
Databases are at the center of modern applications. If the DBMS fails,

applications fail, and if applications fail, business can come to a halt.
Databases interact with almost every component of the IT

infrastructure. The IT infrastructure of today comprises many tools:
• Message queueing software such as MQSeries and MSMQ

• Networking software and protocols such as SNA, VTAM, TCP/IP, and
Novell

Types of DBAs
System DBA
A system DBA focuses on technical rather than business issues
Database Architect
Some organizations create a separate position, database architect, for

design and implementation of new databases.
The database architect is involved in new design and development work

only; he is not involved in maintenance, administration, or tuning of
established databases and applications.
The database architect designs new databases for new or existing

applications.

Types of DBAs
Database Analyst
There is really no set definition for this position. Sometimes junior DBAs are
referred to as database analysts. Sometimes a database analyst performs a
role similar to that of the database architect. Sometimes the data
administrator is referred to as the database analyst or perhaps as the data
analyst. And sometimes a database analyst is just another term used by
some companies instead of database administrator.
Data Modeler
A data modeler is usually responsible for a subset of the DA's responsibilities.
• Collecting data requirements for development projects
• Analyzing the data requirements
• Designing project-based conceptual and logical data models

Types of DBAs
Application DBA
The application DBA focuses on database design and the ongoing support
and administration of databases for a specific application or applications

Types of DBAs
Task-Oriented DBA
Larger organizations sometimes create very specialized DBAs that focus on

a specific DBA task. However, task-oriented DBAs are quite rare outside of
very large IT shops. One example of a task-oriented DBA is a backup-and-
recovery DBA who devotes his entire day to ensuring the recoverability of
the organization's databases.
Data Warehouse Administrator
DBAs specifically to monitor and support the data warehouse environment.

Types of DBAs
Procedural DBAs: Managing Database Logic
The procedural DBA is responsible for those database management

activities that require procedural logic support. He ensures that stored
procedures, triggers, and user-defined functions are effectively planned,
implemented, shared, and reused.
e-DBA
An e-DBA is a DBA who is capable of managing Web-based applications and

their Internet-related issues

DBA Certification
Certification programs are available for most of the popular DBMS platforms
including IBM DB2, Microsoft SQL Server, and Oracle. The idea behind DBA
certification is to ensure that an individual is capable of performing database
administration tasks and duties.

DBA Worst practices
Top 25 DBA worst practices For each wost practices, develop the following
While there may be some disagreement on best practices, there is usually no argument
on worst practices, some of which are listed below (in no particular order): Aspects:
1 Not considering service-level agreements (SLAs) when designing a database
environment and/or not considering the need for scheduled downtime for
1.- Understand the worst practice (describe the
various maintenance activities, such as the installation of service packs.
problem/situation)
2 Defining “disaster” too narrowly and not simulating/practicing a disaster
recovery (DR) plan. Having a DR plan is fine, but how do you know it will
work (and several people can follow it) when required?
2.- Consecuences of the worst practice.
3 Designing a storage system from a capacity perspective alone. 3.- What do you think the best practice must be.
4 Assuming a storage area network (SAN) will meet/exceed performance
requirements. Just because SANs are (typically) expensive, it does not mean
the storage design process can be skipped.
5 Failing to track-align disk partitions and/or formatting them with the default
G1.- 1..3
allocation unit size (4K).
G2.- 4..6
6 Using RAID 5 volumes for write-intensive applications.
7 Failing to validate an I/O subsystem for performance and validity before production
G3.- 7..9
implementation.
G4.- 10..12
8 Virtualizing/consolidating SQL Server instances and databases without consideration
of the scalability, licensing, support, administration, and performance
profile implications.
G5.- 13..15
9 Installing service packs, cumulative updates, or hotfixes without reading the G6.- 16..18
release notes and/or not installing them in a test environment first.
10 Installing all SQL Server features on the off chance they may be needed at
G7.- 19..21
some point in the future. Doing so increases the attack surface area and
results in running unnecessary services that may reduce performance. G8.- 22..24
11 Installing multi-instance clusters without considering the resource implications
of failover situations.
12 Creating logins/jobs with elevated privileges. Implementing least privilege can

be tough work, but it’s essential in locking down a system for maximum security.
13 Changing configuration values from their default settings without adequate

research and/or a detailed change log.
14 Placing data and transaction logs on the same physical disk(s).

Referencias
https://www.youtube.com/watch?v=-MMP20DEJ70
https://es.wikipedia.org/wiki/Administrador_de_base_de_datos

The DBA

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

The DBA

Uploaded by

Copyright:

Available Formats

ADMINISTRACION

Every organization using a database management system

DBMS software is so complex these days that very few people

Database System Concepts 15.3 ©Silberschatz, Korth and Sudarshan

Data is at the center of today's applications; today's

Database System Concepts 15.4 ©Silberschatz, Korth and Sudarshan

A database is an organized store of data wherein the data is

A DBMS is software that enables end users or application

A DBMS is also generally responsible for data integrity, data

Database System Concepts 15.5 ©Silberschatz, Korth and Sudarshan

Database System Concepts 15.6 ©Silberschatz, Korth and Sudarshan

In addition to database management fundamentals, DBAs must

The DBA group, therefore, must have expertise in each of these

The DBA group must be able to act impartially and implement

Database System Concepts 15.7 ©Silberschatz, Korth and Sudarshan

This plan should address all phases of the

Database System Concepts 15.8 ©Silberschatz, Korth and Sudarshan

the rudimentary data requirements must be

the DBA performs a host of duties including

• Is the data no longer required, or do other applications and processes use

Database System Concepts 15.10 ©Silberschatz, Korth and Sudarshan

• Is the data no longer required, or do other applications and processes use

Database System Concepts 15.11 ©Silberschatz, Korth and Sudarshan

Based on the article and the above reviewed,

Database System Concepts 15.12 ©Silberschatz, Korth and Sudarshan

Many organizations combine data administration into the database

•Data administration separates the business aspects of data resource management

Database System Concepts 15.13 ©Silberschatz, Korth and Sudarshan

Another difference between a DA and a DBA is the focus of effort. The DA

• Identifying and cataloging the data required by business users

• Producing conceptual and logical data models to accurately depict

• Creating an enterprise data model that incorporates all of the data

• Setting data policies for the organization

• Identifying data owners and data administrators

• Setting standards for control and usage of data

Database System Concepts 15.14 ©Silberschatz, Korth and Sudarshan

•Furthermore, the DA deals with metadata, as opposed to the DBA, who

•Metadata is often described as data about data; more accurately,

•Data administration is responsible for the business's metadata strategy.

•Examples of metadata include the definition of business names for a data

•Metadata provides the context by which data can be understood.

Database System Concepts 15.15 ©Silberschatz, Korth and Sudarshan

•The DBA generally does not have the skills to communicate

Database System Concepts 15.16 ©Silberschatz, Korth and Sudarshan

Database System Concepts 15.17 ©Silberschatz, Korth and Sudarshan

•The SA ensures that the IT infrastructure is implemented such that the

•The SA may need to work with other technicians to configure transaction

Database System Concepts 15.18 ©Silberschatz, Korth and Sudarshan

Database System Concepts 15.19 ©Silberschatz, Korth and Sudarshan

Database System Concepts 15.20 ©Silberschatz, Korth and Sudarshan

•Throughput defines the overall capability of the computer hardware

•Optimization refers to the analysis of database requests with query

•Contention is the condition in which two or more components

Database System Concepts 15.21 ©Silberschatz, Korth and Sudarshan

Performance Monitoring and Tuning

Database System Concepts 15.22 ©Silberschatz, Korth and Sudarshan

The first component of availability is keeping the DBMS up and running.

An additional component of availability is minimizing the amount of

The DBA must understand all of these aspects of availability and

Database System Concepts 15.23 ©Silberschatz, Korth and Sudarshan

It is the responsibility of the DBA to ensure that data is available only to

• Altering the structure of database objects

• Accessing the system catalog