Database Administration
Chapter 02 –Creating the Database Environment
OVERVIEW
1. Organization’s DBMS Strategy
2. Choosing a DBMS
3. DBMS Architectures
4. Installing the DBMS
5. Upgrading DBMS versions andreleases
6. DBMS Standards and Procedures
DatabaseAdministration3
INTRODUCTION
DatabaseAdministration4
Many business executives and IT professionals without
database management background assume that once
the DBMS is installed, the bulk of the work is done.
Choosing and installing the DBMS is hardly the most
difficult part of aDBA’s job.
Establishing a usable database environment requires a
great deal of skill, knowledge, and consideration.
This chapter will outline the principles involved in
establishing ausable database environment.
ORGANIZATION’S DBMS STRATEGY
DatabaseAdministration5
Large and medium-size organizations typically run
multiple DBMS products
IMS or IDMS and DB2 on themainframe
Oracle and MySQL on several different UNIX servers
Microsoft SQL Server on Windowsservers
Sybase, Ingres,Adabas, and PostgreSQL on various platforms
Single-user PC DBMS products such as Microsoft Access,
Paradox, andFileMaker
Who choose to install all these DBMSs and why?
ORGANIZATION’S DBMS STRATEGY
DatabaseAdministration6
Who choose to install all these DBMSs and why?
Not much thought and planning went into the decision-making
process
Reasonable if your organization has no DBMS and must purchase
one for the first time
DBAs know a new application can be implemented using an existing
DBMS but lack the organizational power or support to reject a
new DBMS proposal
Company purchased a commercial off the-shelf application package
that does not run on any of the current DBMS platforms
Once new DBMS is installed, old applications and databases are
usually not migrated to it. The old DBMS remains and must
continue to be supported
ORGANIZATION’S DBMS STRATEGY
DatabaseAdministration7
So what should be done?
The DBA group should be empowered to make the DBMS
decisions for the organization.
No business unit should be allowed to purchase a DBMS
without the permission of the DBA group
CHOOSING A DBMS
DatabaseAdministration8
DBA group should set a policy to minimize the
number of different DBMS products within
organization
Most of the major DBMS products have similar
features
When choosing a DBMS, it is wise to select a product
from atier-1vendor
Tier 1 represents the largest vendors having the most
heavily implemented and supported products on the
market
CHOOSING A DBMS
Tier – 1
vendors
Choosing a DBMS other than these three should be
done only under specific circumstances
DatabaseAdministration9
CHOOSING A DBMS
Tier – 2
Vendors
➢Quality products, but their installed base is smaller, theirproducts are engineered and marketed for niche purposes,or the companies are smaller with fewer resources
Highperformance
data warehousing
and analytics
capabilities
DatabaseAdministration10
CHOOSING A DBMS
DatabaseAdministration11
PostgreSQL, EnterpriseDB, or MySQL – open source
software movement
ObjectDesign or Versant - object DBMS is important
for a specificproject
Hadoop, Cassandra, andMongoDB - NoSQL DBMS
Choosing any of the lower-tier candidates involve
incurring additional risk
CHOOSING A DBMS
DatabaseAdministration12
Factors to be considered:
Operating system support
Type of organization
Benchmarks
Scalability
Availability of supporting software tools
Technicians
Cost of ownership
Release schedule
Reference customers
FEATURES AND FUNCTIONALITY OF DBMS SOFTWARE
Functionality that used to be supported only with add-
on software or independent programs is increasingly
being added as features of the DBMS
DatabaseAdministration13
DBMS ARCHITECTURES
DatabaseAdministration14
The architecture for the DBMS environment is very critical to the success of the database applicationsFinal DBMS Architecture decision should be made by
a team consists of :Business experts from various departmentsAccounting and legal representatives for software contract issuesDatabase administration representatives (DA, DBA, andSA)Members of the networking group
Operating system expertsOperations control personnel
Programming experts, and any other interested parties
Be sure that the DBMS you select is appropriate for the nature and type of processing you plan to implement
DBMS ARCHITECTURES
DatabaseAdministration15
Enterprise DBMS
Designed for scalability and high performance
Capable of supporting very large databases, a large
number of concurrent users, and multiple types of
applications.
Runs on a large-scale machine, typically a mainframe
or a high-end server running UNIX, LINUX, or
Windows Server.
Multiprocessor support, support for parallel queries,
and other advanced DBMS features
DBMS ARCHITECTURES
DatabaseAdministration16
Departmental DBMS
Workgroup DBMS, serves the middleground
Supports small to medium-size workgroups within an
organization; typically, it runs on a UNIX, Linux, or Windows
server
DBMS ARCHITECTURES
DatabaseAdministration17
Personal DBMS
Designed for a single user, typically on a low- to medium-
powered PC platform
MicrosoftAccess,SQLite, and FileMaker
Oracle Database Personal Edition and DB2 Personal Edition
Never be deployed for multiuser applications
DBMS ARCHITECTURES
DatabaseAdministration18
Mobile DBMS
Specialized version of a departmental or enterprise DBMS
Designed for remote users who are not usually connected to
the network
Enables local database access and modification on a laptop or
handheld device
Provides a mechanism for synchronizing remote database
changes to a centralized enterprise or departmental database
server
DBMS ARCHITECTURES
DatabaseAdministration19
If your organization requires DBMS solutions at
different levels, favor the selection of a group of DBMS
solutions from the same vendor whenever possible
Doing so will minimize differences in access,
development, and administration
Ex : Favor Oracle Database Personal Edition for your
single-user DBMS needs if your organization uses
Oracle as the enterprise DBMS of choice.
DBMS ARCHITECTURES –DBMS CLUSTERING
DatabaseAdministration20
Clustering - Multiple “independent” computing
systems working together as a single, highly available
system
Modern DBMS offers clustering support to enhance
availability and scalability
Two predominant architectures for clustering are :
Shared – nothing
Shared - disk
DBMS ARCHITECTURES –DBMS CLUSTERING
Shared – nothingarchitecture
Each system has its own private resources (memory, disks,
etc.)
DatabaseAdministration21
DBMS ARCHITECTURES –DBMS CLUSTERING
DatabaseAdministration22
Shared – nothingarchitectureThe clustered processors communicate by passing messagesthrough anetwork that interconnects the computers
Only one of the clustered systems can “own” and access aparticular resource ata time.
In the event a failure occurs, resource ownership can bedynamically transferred to another system in the cluster
The main advantage of shared- nothing clustering is scalability
Multi-processors can scale up to thousands of processorsbecause they do not interfere with one another—nothing isshared
Applications with heavy data update requirements areprobably better implemented as shared-nothing
DBMS ARCHITECTURES –BMS CLUSTERING
Shared – diskarchitecture
All the connected systems share the same disk devices
DatabaseAdministration23
DBMS ARCHITECTURES –DBMS CLUSTERING
DatabaseAdministration24
Shared – diskarchitecture
Each processor still has its own private memory, but allthe
processors can directly address all the disks
Shared-disk clustering is better suited to large-enterprise
processing in amainframeenvironment
Preferable for applications and services requiring only
modest shared access to data and for applications or
workloads that are very difficult to partition
DBMS ARCHITECTURES –DBMS CLUSTERING
Shared – disk Vs.shared-nothing
DB2 for z/OS provides shared-disk clustering with its Data Sharing and Parallel Sysplex capabilities;DB2 on non-mainframe platforms uses shared-nothing clustering.Oracle’s Real Application Clusters provide shared-disk clustering.
DatabaseAdministration25
DBMS ARCHITECTURES –DBMS CLUSTERING
DatabaseAdministration26
Benefit of clustering is the enhanced availability that
accrues by combining processors
Can be used for load balancing and failover
HARDWARE ISSUES
DatabaseAdministration27
Hardware and operating system on which the DBMS
will run will greatly impact the reliability, availability, and
scalability (RAS) of the database environment
Other than that Cost, experience, manageability, and
the needs of the applications to be developed must be
considered
CLOUD DATABASE SYSTEMS
DatabaseAdministration28
Delivers DBMS services over the Internet
Improve collaboration among partners, branch offices, remoteworkers, and mobile devices, because the data becomesaccessible as a service
No need to install, set up, patch, or manage the DBMSsoftware because the cloud provider manages and cares forthese administrative tasks
Disadvantages :Data is now stored and controlled by an external agent— the cloud provider
possibility of nefarious agents posing as legitimate customers
Ex : Microsoft SQL Azure build on SQL Server technologiesand is acomponent of the Windows Azure platform
INSTALLING DBMS
DatabaseAdministration29
Prerequisites
Ensuring that an appropriate version of the operating system
is being used
Hardware requirements
Verifying that there is sufficient memory
Any related software to be used with the DBMS is the
proper version and maintenance level
Read the installation guide from cover to cover
STORAGE REQUIREMENTS
DatabaseAdministration30
The system catalog or data dictionary, any othersystem databases required by the DBMS,
Any other system databases required by the DBMS, for example, to support distributed connections or management tools.
Log files that record all changes made to every database.
Start-up or control files that must be accessed by the DBMS when it is started or initialized.
Work files used by the DBMS to sort data or for other processing needs.
Default databases
Temporary database structures used by the DBMS
System dump and error-processing files.
DBA databases used for administration, monitoring, and tuning—forexample, DBA databases used for testing new releases, migrationscripts, and so on.
STORAGE REQUIREMENTS
Log off-loading
DatabaseAdministration31
MEMORY REQUIREMENTS
DatabaseAdministration
DBMS requires a significant amount of memory to cache data
in memory structures in order to avoid I/O
DBMS uses a memory structure called a buffer pool or data
cache to reduce physical I/O requests
32
MEMORY REQUIREMENTS
DatabaseAdministration33
Program cache stores compiled SQL statements,
database authorizations, and database structure blocks
that are used by programs as they are executed
Memory is required additionally for :
handling lock requests
facilitating distributed data requests
sorting data
optimizing processes
processing SQL
CONFIGURING DBMS
DatabaseAdministration34
Configuring the system parameters of the DBMS
controls the manner in which the DBMS functions
and the resources made available to it
DBMS also provides a method to change the system
parameters once the DBMS is operational
System parameters provide :
DBA authorization
number of active database logs
the amount of memory used for data and program caching
turn DBMS features on or off
UPGRADING TO NEW RELEASE - BENEFITS
DatabaseAdministration35
Developers can available themselves of new features
and functionality
For purchased applications, the vendors require the
update to enable specific functionality within the
application
Enhanced performance and availability of features that
can optimize existing applications
Providing a consistent environment for development
and implementation
RISKS OF UPGRADING INTO NEW RELEASE
DatabaseAdministration36
Can result in downtime and lost of business
opportunities if the DBMS upgradeoccurs
Having to convert database structures or discovering
that previously supported features were removed
Cost of upgrading
Performance issued with new releases
Lack of immediate support with supporting software
DATABASE OBJECTS NAMING STANDARDS
DatabaseAdministration37
Without standard database object naming conventions,it will be difficult to identify database objects correctlyand to perform the proper administration tasks.
Database objects include :databases,
tables,
columns, views,indexes,
constraints,
programs,
user-defined data types,
user-defined functions, triggers, and stored procedures
DATABASE OBJECTS NAMING STANDARDS
DatabaseAdministration38
Database naming standard should be designed to minimize name changes across environments
provide a way to differentiate types ofdatabase objects
DBMS can support up to 128-byte table names
Table names should be as descriptive as possibleEx : a good name for the table containing employeeinformation in a human resources system would beHR_EMPLOYEE.
Have an abbreviation list to minimize mistyping andmake it easier for users to remember database objectnames
DATA ADMINISTRATION STANDARDS
DatabaseAdministration39
A clear statement of the organization’s overall policywith regard to data, including its importance to thecompany
Rules for data creation and data ownership
Metadata management policy
Conceptual and logical data modeling guidelines
Organizational data-sharing policies
Guidelines on communication between dataadministration and database administration to ensureeffective database creation and usage
DATABASE ADMINISTRATION STANDARDS
DatabaseAdministration40
How to create a new database or make changes to
existing databases
backup and recovery procedures (including disaster
recovery plans)
communicate the methods used to transform a logical
data model into aphysical database implementation
standards that cover database performance
monitoring and tuning may be useful to document
procedures for overcoming performance problems
SYSTEM ADMINISTRATION STANDARDS
DatabaseAdministration41
DBMS installation and testing procedures
Upgrade policies and procedures
Bug fix and maintenance practices
A checklist of departments to notify for impending
changes
Interface considerations • DBMS storage, usage, and
monitoring procedures
DATABASE APPLICATION DEVELOPMENT STANDARDS
DatabaseAdministration42
A description of how database access differs from flat
file access
SQL coding standards
SQL performance tips and techniques
Program preparation procedures and guidance on
how to embed SQL in an application program
References to other useful programming materials for
teleprocessing monitors, programming languages, and
general application development standards
DATABASE SECURITY STANDARDS
DatabaseAdministration43
Details on what authority to grant for specific types of situations
Ex : if a program is being migrated to production status, what DBMSauthorization must be granted before the program will operatesuccessfully in production
Specific documentation of any special procedures or documentation required for governance- and compliance-related requests
A definitive list of who can approve what types of database authorization requests
Information on any interfaces being used to connect DBMS security with operating system security products
Policies on the use of the WITH GRANT OPTION clause of the SQLGRANT statement and how cascading REVOKEs are to be handledProcedures for notifying the requester that database security hasbeen granted
Procedures for removing security from retiring, relocating, and terminated employees
THANK YOU
DatabaseAdministration44
Top Related