DOCSLIB.ORG

Database Management System

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Database Management System DATABASE MANAGEMENT SYSTEM For COMPUTER SCIENCE DATABASE MANAGEMENT . SYSTEM SYLLABUS ER model. Relational model: relational algebra, tuple calculus, SQL. Integrity constraints, normal forms. File organization, indexing (e.g., B and B+ trees). Transactions and concurrency control. ANALYSIS OF GATE PAPERS Exam Year 1 Mark Ques. 2 Mark Ques. Total 2003 2 3 8 2004 2 5 12 2005 3 4 11 2006 1 4 9 2007 - 6 12 2008 1 5 11 2009 - 5 10 2010 2 2 6 2011 - 2 4 2012 2 5 12 2013 - 3 6 2014 Set-1 2 3 8 2014 Set-2 2 3 8 2014 Set-3 2 3 8 2015 Set-1 2 2 6 2015 Set-2 2 2 6 2015 Set-3 2 2 6 2016 Set-1 4 1 6 2016 Set-2 2 2 6 2017 Set-1 2 3 8 2017 Set-2 2 4 10 201 8 3 2 7 © Copyright Reserved by Gateflix.in No part of this material should be copied or reproduced without permission CONTENTS Topics Page No 1. THE ENTITY – RELATIONSHIP MODEL 1.1 Introduction 1.2 The E – R Model 1.3 Database Administrator (DBA) 01 1.4 The Entity Relationship Diagram 01 01 2. RELATIONAL MODEL 01 2.1 Levels of a Database System 2.2 The Attributes and tuples of a Relation Student 2.3 Keys 04 2.4 Relational Database Design 05 2.5 Network Data Modelling Concepts 06 06 3. TRANSACTIONS 08 3.1 Transactions 3.2 Serializable Schedule 3.3 Recoverability 11 3.4 Recoverable Schedules 12 3.5 Cascade less Schedules 13 3.6 Implementation of Isolation 13 3.7 Transaction Definition in SQL 13 3.8 Testing for Serializability 14 3.9 Tests for View Serializability 14 14 4. QUEL 14 4.1 Quel 4.2 Sequel 4.3 Assign to 15 4.4 SQL 15 4.5 Select Statement 15 4.6 Defining a null Value 15 4.7 Duplicate Rows 16 4.8 Character Strings and Dates 16 4.9 Comparison Operators 16 4.10 Logical Operators 16 4.11 Character Functions 16 17 18 © Copyright Reserved by Gateflix.in No part of this material should be copied or reproduced without permission 4.12 Working with Dates 4.13 Types of Joins 4.14 Group Functions 20 4.15 Sub Queries 21 4.16 Data Definition Language (DDL) 21 4.17 Views 22 4.18 Data Manipulation Language (DML) 23 4.19 Queries 26 4.20 One Possible Database State Corresponding to the 26 Company Scheme 30 4.21 Terminology Used in a Relational Database 4.22 Table Sal Grade 30 33 5. FILE STRUCTURE 33 5.1 Records and Record Types 5.2 B-Trees and other Data Structures 5.3 DBMS 36 5.4 Existence Dependencies 40 43 6. GATE QUESTIONS 46 7. ASSIGNMENT QUESTIONS 51 © Copyright Reserved by Gateflix.in No part of this material should be copied or reproduced without permission 1 THE ENTITY – RELATIONSHIP MODEL 1.1 INTRODUCTION 4) Performance monitoring. 5) Strategy design for backup and An entity is any object, place or activity recovery. about which an enterprise keeps data. It is 6) Authorization checks and validation an object which can have instances or procedures. occurrences. An entity type is a set of 7) Decides the information content. objects which share common properties. The Database Design consists of three 1.4 THE ENTITY RELATIONSHIP DIAGRAM components: Conceptual Design on the basis of user requirements, Data Modeling 1.4.1 RELATIONSHIPS AND RELATIONSHIP (Entity – Relationship Diagrams and SETS Normalization), and Physical Design, and Implementation. The major step in A relationship expresses an association conceptual design is to identify entities and between entities. A relationship set is a set relationships, which reflect the data in a of relationships of the same type. A natural way. The aim of this step is to relationship may also have descriptive specify the conceptual structure of the data. attributes. For example, data (last data of This is known as data modeling. The Entity account access) could be an attribute of the – Relationship (E – R) model is used as an relationship set. information model to develop conceptual structure. 1.4.1.1 MAPPING CARDINALITIES 1.2 THE E – R MODEL It indicates the number of entities with which another entity can be associated via The E – R data model considers the real a relationship. The degree of relationship is world consisting of a set of basic objects called cardinality. and relationships among these objects. A a) One-to-one: An entity in A is associated number of attributes are associated with an with at most one entity in B, and an entity and the attributes describing it. The entity in B is associated with at most set of all entities or relationships of the one entity in A. same type is called the entity set or b) One-to-many: An entity in A is relationship set. associated with any number in B. An entity in B is associated with at least 1.3 DATABASE ADMINISTRATOR (DBA) one entity in A. c) Many-to-one (N:1): An entity in A is All controlling of a database system is done associated with at most one entity in B. by database administrator. An entity in B is associated with any number in A. 1.3.1 FUNCTIONS OF DBA 1.4.2 KEYS 1) Decides the storage structure and Differences between entities must be access strategy. expressed in terms of attributes known as 2) Creation of data dictionary for keys. These facilitate us to uniquely identify statistical analysis. each entity in a set. 3) Responding to changes in requirements. © Copyright Reserved by Gateflix.in No part of this material should be copied or reproduced without permission 1.4.3 SUPER KEY 1.4.7 AGGREGATION It is a set of one or more attributes which The E – R model cannot express put together enable us to identify uniquely relationships among relationships. When an entity in the entity set. would we need such a thing? Consider a database with information 1.4.4 CANDIDATE KEY about employees who work on a particular A super key may contain extraneous project and using a number of machines for attributes, and we are often interested in doing that work. the smallest super key. A super key for We get the E-R diagram shown in Figure. which no subset is a super key is called a candidate key. 1.4.5 PRIMARY KEY It is a candidate key (there may be more than one) chosen by the database designer to identify entities in an entity set. The idea of strong and weak entity sets is related to the existence dependencies such as the member of a strong entity set is a dominant entity, and the member of a weak entity set is a subordinate entity. A weak entity set does not have a primary key, but we need a means of distinguishing among the entities. Relationship sets Working and Uses could be combined into a single set. However, 1.4.6 GENERALIZATION they shouldn’t be, as this would obscure the logical structure of this scheme. The Generalization hides differences and solution is to use aggregation. It is an emphasizes similarities. Distinction is made abstraction through which relationships through attribute inheritance. are treated as higher – level entities. For Attributes of higher – level entity are our example, we can treat the relationship inherited by lower - level entities. set Working and the entity sets Employee and Project as a higher –level entity set called Working. Following figure shows the E-R diagram with aggregation. © Copyright Reserved by Gateflix.in No part of this material should be copied or reproduced without permission Transforming an E-R diagram with aggregation into tabular form is easy. We can create a table for each entity and relationship set as before. The table for relationship set Uses contains a column for each attribute in the primary key of Software Tool and Working. © Copyright Reserved by Gateflix.in No part of this material should be copied or reproduced without permission 2 RELATIONAL MODEL 2.1 LEVELS OF A DATABASE SYSTEM 2.1.1 DOMAINS, ATTRIBUTES, TUPLE & RELATIONS The relational model represents the database as a collection of relations. A domain D is a set of atomic values. By Informally, each relation resembles at automatic we mean that each value in the stable of values or, to some extent, a “flat” domain is indivisible as far as the relational file of records model is concerned. A common method of specifying a domain is to specify a data type from which the data values forming the domain are drawn. It is also useful to specify a for the domain, to help in interpreting its values. Some examples of domains USA – phone – numbers: The set of 10- digit phone numbers valid in the United States. Social –security – numbers: The set of valid 9 – digit social security numbers. Employee – ages: Possible ages of employees of a company; each must be a value between 15 and 80 years old. Academic – department – names: The set of academic department names, such as computer Science, Economics, and Physics, in a university. Academic –department – codes: The set When a relation is thought of as a table of of academic department codes, such as CS, values, each row in the table represents a ECON and PHYS, in a university. collection of related data values. In the The preceding is called logical definition of relational model, each row in the table domains. A data type or format is also represents a fact that typically corresponds specified for each domain.
Load more

Recommended publications
  • ACS-3902 Ron Mcfadyen Slides Are Based on Chapter 5 (7Th Edition)
    ACS-3902 Ron McFadyen Slides are based on chapter 5 (7th edition) (chapter 3 in 6th edition) ACS-3902 1 The Relational Data Model and Relational Database Constraints • Relational model – Ted Codd (IBM) 1970 – First commercial implementations available in early 1980s – Widely used ACS-3902 2 Relational Model Concepts • Database is a collection of relations • Implementation of relation: table comprising rows and columns • In practice a table/relation represents an entity type or relationship type (entity-relationship model … later) • At intersection of a row and column in a table there is a simple value • Row • Represents a collection of related data values • Formally called a tuple • Column names • Columns may be referred to as fields, or, formally as attributes • Values in a column are drawn from a domain of values associated with the column/field/attribute ACS-3902 3 Relational Model Concepts 7th edition Figure 5.1 ACS-3902 4 Domains • Domain – Atomic • A domain is a collection of values where each value is indivisible • Not meaningful to decompose further – Specifying a domain • Name, data type, rules – Examples • domain of department codes for UW is a list: {“ACS”, “MATH”, “ENGL”, “HIST”, etc} • domain of gender values for UW is the list (“male”, “female”) – Cardinality: number of values in a domain – Database implementation & support vary ACS-3902 5 Domain example - PostgreSQL CREATE DOMAIN posint AS integer CHECK (VALUE > 0); CREATE TABLE mytable (id posint); INSERT INTO mytable VALUES(1); -- works INSERT INTO mytable VALUES(-1); -- fails https://www.postgresql.org/docs/current/domains.html ACS-3902 6 Domain example - PostgreSQL CREATE DOMAIN domain_code_type AS character varying NOT NULL CONSTRAINT domain_code_type_check CHECK (VALUE IN ('ApprovedByAdmin', 'Unapproved', 'ApprovedByEmail')); CREATE TABLE codes__domain ( code_id integer NOT NULL, code_type domain_code_type NOT NULL, CONSTRAINT codes_domain_pk PRIMARY KEY (code_id) ) ACS-3902 7 Relation • Relation schema R – Name R and a list of attributes: • Denoted by R (A1, A2, ...,An) • E.g.
    [Show full text]
  • Database Administrator
    Database Administrator Purpose: DGC is looking for a passionate Database Administrator to help support our platform, delivering the content of choice for casino operators and their players. You will be working in a small but high performing IT team to create something special. Online gaming is set to be one of the fastest growing industries in the US as regulation allows online gaming to expand into the various states. Our RGS platform is designed for fast and efficient deployments and seamless integration into a high performing library of online casino games. You will need to assist with the hosting, management and updating of this technology to ensure our success. As an DBA you will implement, design and improve processes relating to the administration of databases to ensure that they function correctly, perform optimally, preserve data and facilitate revenue generation. This role forms part of a rapidly expanding team which will require the ability to support a fast growing infrastructure and customer base. Duties include, but not limited to: • Set and maintain operational database standards on an ongoing basis • Develop and maintain OLAP environments • Develop and maintain OLTP environments • Develop and maintain ETL processes • Enforce and improve database integrity and performance using sound design principles and implementation of database design standards • Design and enforce data security policies to eliminate unauthorised access to data on managed data systems in accordance with IT Services technical specifications and business requirements • Ensure that effective data redundancy; archiving, backup and recovery mechanisms are in place to prevent the loss of data • Set up configurable pre-established jobs to automatically run daily in order to monitor and maintain the operational databases • Provide 24-hour standby support by being available on a 24/7 basis during specified periods This job description is not intended to be an exhaustive list of responsibilities.
    [Show full text]
  • Relational Database Design Chapter 7
    Chapter 7: Relational Database Design Chapter 7: Relational Database Design First Normal Form Pitfalls in Relational Database Design Functional Dependencies Decomposition Boyce-Codd Normal Form Third Normal Form Multivalued Dependencies and Fourth Normal Form Overall Database Design Process Database System Concepts 7.2 ©Silberschatz, Korth and Sudarshan 1 First Normal Form Domain is atomic if its elements are considered to be indivisible units + Examples of non-atomic domains: Set of names, composite attributes Identification numbers like CS101 that can be broken up into parts A relational schema R is in first normal form if the domains of all attributes of R are atomic Non-atomic values complicate storage and encourage redundant (repeated) storage of data + E.g. Set of accounts stored with each customer, and set of owners stored with each account + We assume all relations are in first normal form (revisit this in Chapter 9 on Object Relational Databases) Database System Concepts 7.3 ©Silberschatz, Korth and Sudarshan First Normal Form (Contd.) Atomicity is actually a property of how the elements of the domain are used. + E.g. Strings would normally be considered indivisible + Suppose that students are given roll numbers which are strings of the form CS0012 or EE1127 + If the first two characters are extracted to find the department, the domain of roll numbers is not atomic. + Doing so is a bad idea: leads to encoding of information in application program rather than in the database. Database System Concepts 7.4 ©Silberschatz, Korth and Sudarshan 2 Pitfalls in Relational Database Design Relational database design requires that we find a “good” collection of relation schemas.
    [Show full text]
  • Data Definition Language
    1 Structured Query Language SQL, or Structured Query Language is the most popular declarative language used to work with Relational Databases. Originally developed at IBM, it has been subsequently standard- ized by various standards bodies (ANSI, ISO), and extended by various corporations adding their own features (T-SQL, PL/SQL, etc.). There are two primary parts to SQL: The DDL and DML (& DCL). 2 DDL - Data Definition Language DDL is a standard subset of SQL that is used to define tables (database structure), and other metadata related things. The few basic commands include: CREATE DATABASE, CREATE TABLE, DROP TABLE, and ALTER TABLE. There are many other statements, but those are the ones most commonly used. 2.1 CREATE DATABASE Many database servers allow for the presence of many databases1. In order to create a database, a relatively standard command ‘CREATE DATABASE’ is used. The general format of the command is: CREATE DATABASE <database-name> ; The name can be pretty much anything; usually it shouldn’t have spaces (or those spaces have to be properly escaped). Some databases allow hyphens, and/or underscores in the name. The name is usually limited in size (some databases limit the name to 8 characters, others to 32—in other words, it depends on what database you use). 2.2 DROP DATABASE Just like there is a ‘create database’ there is also a ‘drop database’, which simply removes the database. Note that it doesn’t ask you for confirmation, and once you remove a database, it is gone forever2. DROP DATABASE <database-name> ; 2.3 CREATE TABLE Probably the most common DDL statement is ‘CREATE TABLE’.
    [Show full text]
  • Oracle Database Advanced Application Developer's Guide, 11G Release 2 (11.2) E17125-03
    Oracle® Database Advanced Application Developer's Guide 11g Release 2 (11.2) E17125-03 August 2010 Oracle Database Advanced Application Developer's Guide, 11g Release 2 (11.2) E17125-03 Copyright © 1996, 2010, Oracle and/or its affiliates. All rights reserved. Primary Author: Sheila Moore Contributing Authors: D. Adams, L. Ashdown, M. Cowan, J. Melnick, R. Moran, E. Paapanen, J. Russell, R. Strohm, R. Ward Contributors: D. Alpern, G. Arora, C. Barclay, D. Bronnikov, T. Chang, L. Chen, B. Cheng, M. Davidson, R. Day, R. Decker, G. Doherty, D. Elson, A. Ganesh, M. Hartstein, Y. Hu, J. Huang, C. Iyer, N. Jain, R. Jenkins Jr., S. Kotsovolos, V. Krishnaswamy, S. Kumar, C. Lei, B. Llewellyn, D. Lorentz, V. Moore, K. Muthukkaruppan, V. Moore, J. Muller, R. Murthy, R. Pang, B. Sinha, S. Vemuri, W. Wang, D. Wong, A. Yalamanchi, Q. Yu This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this software or related documentation is delivered to the U.S.
    [Show full text]
  • SQL Stored Procedures
    Agenda Key:31MA Session Number:409094 DB2 for IBM i: SQL Stored Procedures Tom McKinley ([email protected]) DB2 for IBM i consultant IBM Lab Services 8 Copyright IBM Corporation, 2009. All Rights Reserved. This publication may refer to products that are not currently available in your country. IBM makes no commitment to make available any products referred to herein. What is a Stored Procedure? • Just a called program – Called from SQL-based interfaces via SQL CALL statement • Supports input and output parameters – Result sets on some interfaces • Follows security model of iSeries – Enables you to secure your data – iSeries adopted authority model can be leveraged • Useful for moving host-centric applications to distributed applications 2 © 2009 IBM Corporation What is a Stored Procedure? • Performance savings in distributed computing environments by dramatically reducing the number of flows (requests) to the database engine – One request initiates multiple transactions and processes R R e e q q u u DB2 for i5/OS DB2DB2 for for i5/OS e e AS/400 s s t t SP o o r r • Performance improvements further enhanced by the option of providing result sets back to ODBC, JDBC, .NET & CLI clients 3 © 2009 IBM Corporation Recipe for a Stored Procedure... 1 Create it CREATE PROCEDURE total_val (IN Member# CHAR(6), OUT total DECIMAL(12,2)) LANGUAGE SQL BEGIN SELECT SUM(curr_balance) INTO total FROM accounts WHERE account_owner=Member# AND account_type IN ('C','S','M') END 2 Call it (from an SQL interface) over and over CALL total_val(‘123456’, :balance) 4 © 2009 IBM Corporation Stored Procedures • DB2 for i5/OS supports two types of stored procedures 1.
    [Show full text]
  • Reactive Relational Database Connectivity
    R2DBC - Reactive Relational Database Connectivity Ben Hale<[email protected]>, Mark Paluch <[email protected]>, Greg Turnquist <[email protected]>, Jay Bryant <[email protected]> Version 0.8.0.RC1, 2019-09-26 © 2017-2019 The original authors. Copies of this document may be made for your own use and for distribution to others, provided that you do not charge any fee for such copies and further provided that each copy contains this Copyright Notice, whether distributed in print or electronically. 1 Preface License Specification: R2DBC - Reactive Relational Database Connectivity Version: 0.8.0.RC1 Status: Draft Specification Lead: Pivotal Software, Inc. Release: 2019-09-26 Copyright 2017-2019 the original author or authors. Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at https://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. Foreword R2DBC brings a reactive programming API to relational data stores. The Introduction contains more details about its origins and explains its goals. This document describes the first and initial generation of R2DBC. Organization of this document This document is organized into the following parts: • Introduction • Goals • Compliance • Overview • Connections • Transactions 2 • Statements • Batches • Results • Column and Row Metadata • Exceptions • Data Types • Extensions 3 Chapter 1.
    [Show full text]
  • Database Administrator
    Contra Costa Community College District – Classification Specification DATABASE ADMINISTRATOR Class Code OT Status EEO Category Represented Salary Effective Date Status Pages Status Grade Non-Exempt Technical/Paraprofessional PEU Local 1 75 07/01/2017 Classified 1 of 2 DEFINITION To support the relational databases on the various computer platform environments; to assist in the development, creation and maintenance of relational databases for present and future requirements; and to recommend and maintain security measures for the database environment. DISTINGUISHING CHARACTERISTICS Database Administrator – This is the journey-level classification in the Database Administrator Series. Positions in this classification are responsible for moderately complex projects with general supervision provided by the appropriate manager. Knowledge of database management theory and practice is reasonably extensive, and understanding of moderately complex database concepts is critical. Database Administrator, Senior – This is the most advanced level in the Database Administrator series. Positions in this classification are responsible for highly complex projects with general direction provided by the appropriate manager. Knowledge of database management theory and practice is extensive, and understanding of complex database concepts is critical. SUPERVISION RECEIVED AND EXERCISED Receives supervision from a departmental supervisor or manager. May receive technical or functional supervision from higher-level departmental personnel. May provide training and direction to student assistants or other assigned staff. EXAMPLES OF DUTIES Duties may include, but are not limited to, the following: Documents, designs, develops, optimizes, and improves new and existing logical and physical databases for custom and commercial applications to meet the changing needs of the user community. Coordinates database development as part of project team and individually, applying knowledge of database design standards, configuration, tools and services, and database management system.
    [Show full text]
  • Relational Database Design: FD's & BCNF
    CS145 Lecture Notes #5 Relational Database Design: FD's & BCNF Motivation Automatic translation from E/R or ODL may not produce the best relational design possible Sometimes database designers like to start directly with a relational design, in which case the design could be really bad Notation , , ... denote relations denotes the set of all attributes in , , ... denote attributes , , ... denote sets of attributes Functional Dependencies A functional dependency (FD) has the form , where and are sets of attributes in a relation Formally, means that whenever two tuples in agree on all the attributes of , they must also agree on all the attributes of Example: FD's in Student(SID, SS#, name, CID, grade) Some FD's are more interesting than others: Trivial FD: where is a subset of Example: Nontrivial FD: where is not a subset of Example: Completely nontrivial FD: where and do not overlap Example: Jun Yang 1 CS145 Spring 1999 Once we declare that an FD holds for a relation , this FD becomes a part of the relation schema Every instance of must satisfy this FD This FD should better make sense in the real world! A particular instance of may coincidentally satisfy some FD But this FD may not hold for in general Example: name SID in Student? FD's are closely related to: Multiplicity of relationships Example: Queens, Overlords, Zerglings Keys Example: SID, CID is a key of Student Another de®nition of key: A set of attributes is a key for if (1) ; i.e., is a superkey (2) No proper subset of satis®es (1) Closures of Attribute Sets Given , a set of FD's
    [Show full text]
  • Junior Database Administrator
    JUNIOR DATABASE ADMINISTRATOR The National Association of Counties (NACo) is seeking a highly organized individual with great attention to detail for the position of Database Administrator (DBA). The DBA ensures data quality for the entire organization. This position is responsible for maintaining database applications, ensuring information is accurate and entered in a timely manner to support NACo departments and program requirements. The position is also responsible for data entry, data structure, report customization, and analysis and data quality control. The database administrator (DBA) is responsible for the performance, integrity and security of NACo’s database. The DBA will be involved in the planning and development of the database, as well as in troubleshooting any issues on behalf of the users. The DBA will ensure data remains consistent across the database, data is clearly defined, users access data concurrently and in a form that suits their needs, and ensure all data is retrievable in an emergency. RESPONSIBILITIES: • Establish the needs of users and monitor user access and security • Monitor performance and manage parameters in order to provide fast responses to front-end users • Map out the conceptual design for a planned database • Ensure all data is retrievable in an emergency • Consider both back-end organization of data and front-end accessibility for end-users • Refine the logical design so that it can be translated into a specific data model • Install and test new versions of the database management system (DBMS)
    [Show full text]
  • Introduction to Database
    ST. LAWRENCE HIGH SCHOOL A Jesuit Christian Minority Institution STUDY MATERIAL - 12 Subject: COMPUTER SCIENCE Class - 12 Chapter: DBMS Date: 01/08/2020 INTRODUCTION TO DATABASE What is Database? The database is a collection of inter-related data which is used to retrieve, insert and delete the data efficiently. It is also used to organize the data in the form of a table, schema, views, and reports, etc. For example: The college Database organizes the data about the admin, staff, students and faculty etc. Using the database, you can easily retrieve, insert, and delete the information. Database Management System Database management system is a software which is used to manage the database. For example: MySQL, Oracle, etc. are a very popular commercial database which is used in different applications. DBMS provides an interface to perform various operations like database creation, storing data in it, updating data, creating a table in the database and a lot more. It provides protection and security to the database. In the case of multiple users, it also maintains data consistency. DBMS allows users the following tasks: Data Definition: It is used for creation, modification, and removal of definition that defines the organization of data in the database. Data Updation: It is used for the insertion, modification, and deletion of the actual data in the database. Data Retrieval: It is used to retrieve the data from the database which can be used by applications for various purposes. User Administration: It is used for registering and monitoring users, maintain data integrity, enforcing data security, dealing with concurrency control, monitoring performance and recovering information corrupted by unexpected failure.
    [Show full text]
  • Database Administrator
    OFFICE OF THE STATE AUDITOR DATABASE ADMINISTRATOR Posting Number 2015-26 SALARY RANGE (Grade 14A): $59,452.85 to $89,178.87 (Commensurate with experience) GENERAL STATEMENT OF DUTIES The Office of the State Auditor is seeking an experienced Database Administrator responsible for managing databases on Microsoft SQL Server platform. The DBA will administer databases on several Microsoft Windows database servers with databases that serve internally developed applications, external third party applications, as well as data warehouses. The DBA will help migrate older databases to latest versions, and implement advanced database technologies such as columnar databases, tabular model, database replications as well as implement uniform access control practices and advise on other technologies that may help the organization. SUPERVISION RECEIVED Receives supervision and direction from the Assistant Director of Data Analytics. SUPERVISION EXERCISED Provides technical supervision over 1-3 contract personnel on an as needed or by project basis DUTIES AND RESPONSIBILITIES • Setup, upgrade, and manage MS SQL Server database hosts by installing and configuring software. • Manage database schemas and schema objects such as constraints, indexes, etc. to provide application support and database tuning. • Manage storage by understanding and reporting the current space utilization, organizing current data, and developing proper mechanisms to ensure storage is efficiently utilized. This may also include monitoring and reporting of storage utilization and cleanup/removal of orphan data. • Inventory the current database servers and individual databases by performing discovery or working with other team members, then ensure that all databases are adequately being maintained. • Inventory the current access control mechanisms used in the organization and modify the access to ensure that a uniform access control mechanism is implemented consistent with security policies.
    [Show full text]