Database administration

Function of managing and maintaining DBMS software

This article includes a list of general references, but it lacks sufficient corresponding inline citations. Please help to improve this article by introducing more precise citations. (March 2011) (Learn how and when to remove this message)

|

Database administration is the function of managing and maintaining database management systems (DBMS) software. Mainstream DBMS software such as Oracle, IBM Db2 and Microsoft SQL Server need ongoing management. As such, corporations that use DBMS software often hire specialized information technology personnel called database administrators or DBAs.

## Responsibilities

[edit]

* Installation, configuration and upgrading of Database server software and related products.
* Evaluate Database features and Database related products.
* Establish and maintain sound backup and recovery policies and procedures.
* Take care of the Database design and implementation.
* Implement and maintain database security (create and maintain users and roles, assign privileges).
* Database tuning and performance monitoring.
* Application tuning and performance monitoring.
* Setup and maintain documentation and standards.
* Plan growth and changes (capacity planning).
* Work as part of a team and provide 24/7 support when required.
* Do general technical troubleshooting and give cons.
* Database recovery

## Types

[edit]

There are three types of DBAs:

1. Systems DBAs (also referred to as physical DBAs, operations DBAs or production Support DBAs): focus on the physical aspects of database administration such as DBMS installation, configuration, patching, upgrades, backups, restores, refreshes, performance optimization, maintenance and disaster recovery.
2. Development DBAs: focus on the logical and development aspects of database administration such as data model design and maintenance, DDL (data definition language) generation, SQL writing and tuning, coding stored procedures, collaborating with developers to help choose the most appropriate DBMS feature/functionality and other pre-production activities.
3. Application DBAs: usually found in organizations that have purchased 3rd party application software such as ERP (enterprise resource planning) and CRM (customer relationship management) systems. Examples of such application software includes Oracle Applications, Siebel and PeopleSoft (both now part of Oracle Corp.) and SAP. Application DBAs straddle the fence between the DBMS and the application software and are responsible for ensuring that the application is fully optimized for the database and vice versa. They usually manage all the application components that interact with the database and carry out activities such as application installation and patching, application upgrades, database cloning, building and running data cleanup routines, data load process management, etc.

In larger organizations, individuals typically specialize in a specific type of database administration. However, in smaller organizations, it's common for a single person or team to handle multiple database administration roles.

## Automation of database administration

[edit]

The degree to which the administration of a database is automated dictates the skills and personnel required to manage databases. On one end of the spectrum, a system with minimal automation will require significant experienced resources to manage; perhaps 5-10 databases per DBA. Alternatively an organization might choose to automate a significant amount of the work that could be done manually therefore reducing the skills required to perform tasks. As automation increases, the personnel needs of the organization splits into highly skilled workers to create and manage the automation and a group of lower skilled "line" DBAs who simply execute the automation.

Database administration work is complex, repetitive, time-consuming and requires significant training. Since databases hold valuable and mission-critical data, companies usually look for candidates with multiple years of experience. Database administration often requires DBAs to put in work during off-hours (for example, for planned after hours downtime, in the event of a database-related outage or if performance has been severely degraded). DBAs are commonly well compensated for the long hours.

One key skill required and often overlooked when selecting a DBA is database recovery (a part of disaster recovery). It is not a case of “if” but a case of “when” a database suffers a failure, ranging from a simple failure to a full catastrophic failure. The failure may be data corruption, media failure, or user induced errors. In either situation the DBA must have the skills to recover the database to a given point in time to prevent a loss of data.

## Database administration tools

[edit]

Often, the DBMS software comes with certain tools to help DBAs manage the DBMS. Such tools are called native tools. For example, Microsoft SQL Server comes with SQL Server Management Studio and Oracle has tools such as SQL*Plus and Oracle Enterprise Manager/Grid Control. In addition, 3rd parties such as BMC, Quest Software, Embarcadero Technologies, patchVantage and SQL Maestro Group offer GUI tools to monitor the DBMS and help DBAs carry out certain functions inside the database more easily.

Another kind of database software exists to manage the provisioning of new databases and the management of existing databases and their related resources. The process of creating a new database can consist of hundreds or thousands of unique steps from satisfying prerequisites to configuring backups where each step must be successful before the next can start. A human cannot be expected to complete this procedure in the same exact way time after time - exactly the goal when multiple databases exist.

As the number of DBAs grows, without automation the number of unique configurations frequently grows to be costly/difficult to support. All of these complicated procedures can be modeled by the best DBAs into database automation software and executed by the standard DBAs. Software has been created specifically to improve the reliability and repeatability of these procedures such as Stratavia's Data Palette and GridApp Systems Clarity.

## The impact of IT and cloud automation

[edit]

Automated Database operations has grown since 2009, following Amazon Web Services introduction of AWS RDS, providing automated and managed database as a service.[1] Microsoft Azure launched a similar automated database as a service in 2010, with SQL Azure, providing automated backups, with geo-replication and high availability. The introduction of docker (software) containers has enhanced support for fast delivery of containerized database instances, and both Amazon Web Services and Microsoft Azure have enhanced automated support for containers in their respective services.

Third party support for database container images has grown, including MongoDB, PostgreSQL, MySQL from Oracle, and Microsoft SQL Server from Microsoft, and from independent port's of docker (software) from Windocks [2] Kubernetes, and the development of the Kubernetes Operator pattern by CoreOS, further extended the ability to orchestrate database container.[3] Kubernetes Operators have been used by third parties to enable the ability to automate database administration, including deployment of instances of a database, upgrade database versions, or perform backups.[4]

Newer technologies such as Stratavia's Data Palette suite and GridApp Systems Clarity have begun to increase the automation of databases causing the reduction of database related tasks. However at best this only reduces the amount of mundane, repetitive activities and does not eliminate the need for DBAs. The intention of DBA automation is to enable DBAs to focus on more proactive activities around database architecture, deployment, performance and service level management.

Every database requires a database owner account that can perform all schema management operations. This account is specific to the database and cannot log into Data Director. You can add database owner accounts after database creation. Data Director users must log in with their database-specific credentials to view the database, its entities, and its data or to perform database management tasks. Database administrators and application developers can manage databases only if they have appropriate permissions and roles granted to them by the organization administrator. The permissions and roles must be granted on the database group or on the database, and they only apply within the organization in which they are granted.

## Learning database administration

[edit]

There are several education institutes that offer professional courses, including late-night programs, to allow candidates to learn database administration. DBMS vendors such as Oracle, Microsoft and IBM offer certification programs to help companies to hire qualified DBA practitioners. College degree in Computer Science or related field is helpful but not necessarily a prerequisite.

## See also

[edit]

* Column-oriented DBMS
* Data warehouse
* Directory service
* Distributed database management system
* Hierarchical model
* Navigational database
* Network model
* Object model
* Object database (OODBMS)
* Object–relational database (ORDBMS)
* Run Book Automation (RBA)
* Relational model (RDBMS)
* Comparison of relational database management systems
* Comparison of database tools
* SQL is a language for database management

## References

[edit]

1. ^ Perry, Yifat (2020-05-18). "AWS Database". NetApp BlueXP.
2. ^ Yegulalp, Serdar, "Windocks does what Docker and Microsoft can't do", InfoWorld
3. ^ CoreOS Introduces "Operators" to Simplify Configuration and Management of Modern Distributed Applications
4. ^ Kubernetes Operators in Depth

## External links

[edit]

* "A set theoretic data structure and retrieval language". SIGIR Forum. 7 (4). ACM Special Interest Group on Information Retrieval: 45–55\. Winter 1972. doi:10.1145/1095495.1095500. S2CID 16601739.
* Thomas Haigh (June 2006). "Origins of the Data Base Management System" (PDF). SIGMOD Record. 35 (2). ACM Special Interest Group on Management of Data.

* v
* t
* e

Database

Main|

* Requirements
* Theory
* Database object
* Models
* Database management system
* Machine
* Engine
* Server
* Application
* Connection
* datasource
* DSN
* Administrator
* Synonym
* Lock
* Types
* Tools

Languages|

* Data definition
* Data manipulation
* Query
* information retrieval

Security|

* Activity monitoring
* Audit
* Forensics
* Negative database

Design|

* Entities and relationships (and Enhanced notation)
* Normalization
* Schema
* Refactoring
* Cardinality

Programming|

* Abstraction layer
* Object–relational mapping

Management|

* Virtualization
* Tuning
* caching
* Migration
* Preservation
* Integrity

Lists of|

* Academic
* Biological
* Biodiversity
* Facial expression
* Online
* Online music
* Online real estate

See also|

* Database-centric architecture
* Intelligent database
* Two-phase locking
* Locks with ordered sharing
* Load file
* Publishing
* Halloween Problem
* Log shipping

WikiProject Category

* v
* t
* e

Database management systems

Types|

* Object-oriented
* comparison
* Relational
* list
* comparison
* Key–value
* Column-oriented
* list
* Document-oriented
* Wide-column store
* Graph
* NoSQL
* NewSQL
* In-memory
* list
* Multi-model
* comparison
* Cloud
* Blockchain-based database

Concepts|

* Database
* ACID
* Armstrong's axioms
* Codd's 12 rules
* CAP theorem
* CRUD
* Null
* Candidate key
* Foreign key
* PACELC design principle
* Superkey
* Surrogate key
* Unique key

Objects|

* Relation
* table
* column
* row
* View
* Transaction
* Transaction log
* Trigger
* Index
* Stored procedure
* Cursor
* Partition

Components|

* Concurrency control
* Data dictionary
* JDBC
* XQJ
* ODBC
* Query language
* Query optimizer
* Query rewriting system
* Query plan

Functions|

* Administration
* Query optimization
* Replication
* Sharding

Related topics|

* Database models
* Database normalization
* Database storage
* Distributed database
* Federated database system
* Referential integrity
* Relational algebra
* Relational calculus
* Relational model
* Object–relational database
* Transaction processing

* Category
* Outline

Authority control databases: National |

* Czech Republic

|

*[v]: View this template
*[t]: Discuss this template
*[e]: Edit this template