DOCSLIB.ORG

6660 Database Design and Management (Oracle)

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
6660 Database Design and Management (Oracle) Database Design and Management (Oracle) 6660 36 weeks Table of Contents Acknowledgments ......................................................................................................................................... 2 Course Description ........................................................................................................................................ 3 Task Essentials Table .................................................................................................................................... 3 Curriculum Framework ............................................................................................................................... 10 Exploring Database Technologies .............................................................................................................. 10 Identifying Business Requirements ............................................................................................................ 15 Examining Entity-Relationship Basics ....................................................................................................... 18 Applying Design Concepts to Database Models ......................................................................................... 21 Transitioning from Design Concepts to Database Management ................................................................. 27 Writing Structured Query Language (SQL) Statements ............................................................................. 30 Restricting and Sorting Data Using SQL .................................................................................................... 33 Performing Single-Row Functions.............................................................................................................. 39 Using JOIN Tables ...................................................................................................................................... 44 Aggregating Data Using GROUP Functions .............................................................................................. 45 Applying Advanced Data Selection Techniques ........................................................................................ 48 Applying Data Manipulation Language ...................................................................................................... 52 Modifying and Managing Tables ................................................................................................................ 57 Defining Database Constraints.................................................................................................................... 62 Creating and Managing Views .................................................................................................................... 64 Creating Additional Database Objects ........................................................................................................ 67 Maintaining Database Security and System Security ................................................................................. 72 Making Database Transactions ................................................................................................................... 75 Preparing for Industry Certification ............................................................................................................ 77 SOL Correlation by Task ............................................................................................................................ 80 Teacher Resources ...................................................................................................................................... 84 1 Cyber Security and Cyber Forensics Infusion Units ................................................................................... 88 Entrepreneurship Infusion Units ................................................................................................................. 88 Appendix: Credentials, Course Sequences, and Career Cluster Information ............................................. 89 Acknowledgments The components of this instructional framework were developed by the following curriculum development panelists: Jill Anderson, Instructor, Matoaca High School Center for Information Technology, Chesterfield County Public Schools Frank Baber, Director, Oracle Cloud Solution Hubs Developer Innovation Team, Oracle, Reston Gail Drake, Instructor, Battlefield High School, Prince William County Public Schools Denise Hobbs, Regional Director, North America, Oracle, Albuquerque, New Mexico Lisa Palombo, Senior Curriculum Developer, Oracle, St. George, Utah Brian Thomas, Instructor, James Wood High School, Frederick County Public Schools Correlations to the Virginia Standards of Learning were reviewed and updated by: Leslie R. Bowers, English Teacher (ret.), Newport News Public Schools Vickie L. Inge, Mathematics Committee Member, Virginia Mathematics and Science Coalition Anne F. Markwith, New Teacher Mentor (Science), Gloucester County Public Schools Michael Nagy, Social Studies Department Chair, Rustburg High School, Campbell County Public Schools The framework was edited and produced by the CTE Resource Center: Nathan K. Pope, Writer/Editor Kevin P. Reilly, Administrative Coordinator Virginia Department of Education Staff Judith P. Sams, Specialist, Business and Information Technology and Related Clusters Dr. Tricia S. Jacobs, CTE Coordinator of Curriculum and Instruction Dr. David S. Eshelman, Director, Workforce Development and Initiatives George R. Willcox, Director, Operations and Accountability Office of Career, Technical, and Adult Education Virginia Department of Education 2 Copyright © 2019 Course Description Suggested Grade Level: 10 or 11 This course includes database design and Structured Query Language (SQL) programming. Students study database fundamentals, including database development, modeling, design, and normalization. In addition, students are introduced to database programming with SQL. Students gain the skills and knowledge needed to use features of database software and programming to manage and control access to data. Students will prepare for the first of two certification exams. Recommended prerequisite: Information Technology Fundamentals 6670 Task Essentials Table • Tasks/competencies designated by plus icons ( ) in the left-hand column(s) are essential • Tasks/competencies designated by empty-circle icons ( ) are optional • Tasks/competencies designated by minus icons ( ) are omitted • Tasks marked with an asterisk (*) are sensitive. Task 6660 Tasks/Competencies Number Exploring Database Technologies 39 Research the history of databases. 40 List the major types of databases. 41 Distinguish between a conceptual and a physical database model. 42 Compare the structure of relational and non-relational database structures. 43 Identify the characteristics of a relational database. 44 Examine the database development life cycle. 45 Research the future direction of database technologies. Identifying Business Requirements 3 46 Describe the process of modeling business requirements. 47 Apply business concepts to the database model. 48 Define entities among elements of significance. 49 Define attributes of each entity. 50 Select unique identifiers (UIDs). 51 Define types of unique identifiers. 52 Define business rules. Examining Entity-Relationship Basics 53 Analyze entities for relationships that exist among them. 54 Distinguish among relationship types. 55 Describe relationship transferability. 56 Name relationships. 57 Explain relationship optionality. 58 Explain relationship degree/cardinality. Applying Design Concepts to Database Models 59 Identify elements of the graphic representation of a database model. 60 Define drawing conventions for readability. 61 Illustrate business rules in an entity-relationship model. 62 Define the normalization process. 63 Perform the normalization process. 64 Resolve many-to-many relationships. 65 Model hierarchical data. 66 Model recursive relationships. 67 Model exclusive relationships. 4 68 Define relational-database terminology. 69 Define a fact and dimension. 70 Verbalize a diagram's relationship notation. Transitioning from Design Concepts to Database Management 71 Summarize the database-design process. 72 Convert a conceptual design to a physical database model. 73 Map simple entities, attributes, and primary keys. 74 Identify data constraints. 75 Map relationships to foreign keys. Writing Structured Query Language (SQL) Statements 76 Describe SQL. 77 Distinguish among categories of SQL statements. 78 Demonstrate the syntax for select statements (projection). 79 Demonstrate methods for selecting columns and arithmetic expressions (selection). 80 Incorporate column alias and literals in a SELECT statement. 81 Describe operator precedence. 82 Describe methods for displaying a table. Restricting and Sorting Data Using SQL 83 Restrict data, using the WHERE clause. 84 Define comparison operators (e.g., =, >, <, >=, <=, <>, !=) 85 Restrict data, using the BETWEEN ... AND and IN clauses. 86 Restrict data, using wildcards and patterns within the LIKE condition. 87 Demonstrate the use of the ESCAPE character with wildcard characters. 5 88 Restrict (or specify) data containing nulls, using the IS (NOT) NULL clause. 89 Demonstrate the use of two or more conditional statements using logical operators (i.e., AND, OR, NOT). 90 Sort data by using ResultSet with the ORDER BY clause. Performing Single-Row Functions 91 Explain
Load more

Recommended publications
  • Evolution of Database Technology
    Introduction and Database Technology By EM Bakker September 11, 2012 Databases and Data Mining 1 DBDM Introduction Databases and Data Mining Projects at LIACS Biological and Medical Databases and Data Mining CMSB (Phenotype Genotype), DIAL CGH DB Cyttron: Visualization of the Cell GRID Computing VLe: Virtual Lab e-Science environments DAS3/DAS4 super computer Research on Fundamentals of Databases and Data Mining Database integration Data Mining algorithms Content Based Retrieval September 11, 2012 Databases and Data Mining 2 DBDM Databases (Chapters 1-7): The Evolution of Database Technology Data Preprocessing Data Warehouse (OLAP) & Data Cubes Data Cubes Computation Grand Challenges and State of the Art September 11, 2012 Databases and Data Mining 3 DBDM Data Mining (Chapters 8-11): Introduction and Overview of Data Mining Data Mining Basic Algorithms Mining data streams Mining Sequence Patterns Graph Mining September 11, 2012 Databases and Data Mining 4 DBDM Further Topics Mining object, spatial, multimedia, text and Web data Mining complex data objects Spatial and spatiotemporal data mining Multimedia data mining Text mining Web mining Applications and trends of data mining Mining business & biological data Visual data mining Data mining and society: Privacy-preserving data mining September 11, 2012 Databases and Data Mining 5 [R] Evolution of Database Technology September 11, 2012 Databases and Data Mining 6 Evolution of Database Technology 1960s: (Electronic) Data collection, database creation, IMS
    [Show full text]
  • 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
    PINELLAS COUNTY SCHOOL DISTRICT, FLORIDA PCSB: 8155 FLSA: Exempt Pay Grade: E08 PTS DATABASE ADMINISTRATOR REPORTS TO: Director, Application Support and Development SUPERVISES: Senior Application Specialist Programmer Analyst QUALIFICATIONS: IT-related bachelor’s degree from an accredited college or university preferably in MIS or a related area plus five (5) years progressively responsible experience in programming, systems analysis, systems design work, database programming experience writing and maintaining complex database objects using Microsoft SQL Server to include three (3) years of information systems project management experience. Database management and experience using DB2, MySQL, SQL Server Integration Services, SQL Server Analysis Services and SQL Server Reporting Services is required. Experience with hardware and applications required; or an equivalent combination of education, training, and related Pinellas County School Board experience. Microsoft technology certification desired in Microsoft Certified Professional (MCP), Microsoft Certified Application Developer (MCAD), Microsoft Certified Solution Developer (MCSD), and/or Microsoft Certified Database Administrator (MCDBA). MAJOR FUNCTION Responsible for creating data structures and database management capabilities to enable the development of application solutions involving operational databases and solutions utilizing business intelligence and data warehousing databases. Accomplishes this with strong troubleshooting, performance tuning skills, strong problem-solving,
    [Show full text]
  • Form Follows Function Model-Driven Engineering for Clinical Trials
    Form Follows Function Model-Driven Engineering for Clinical Trials Jim Davies1, Jeremy Gibbons1, Radu Calinescu2, Charles Crichton1, Steve Harris1, and Andrew Tsui1 1 Department of Computer Science, University of Oxford Wolfson Building, Parks Road, Oxford OX1 3QD, UK http://www.cs.ox.ac.uk/firstname.lastname/ 2 Computer Science Research Group, Aston University Aston Triangle, Birmingham B4 7ET, UK http://www-users.aston.ac.uk/~calinerc/ Abstract. We argue that, for certain constrained domains, elaborate model transformation technologies|implemented from scratch in general- purpose programming languages|are unnecessary for model-driven en- gineering; instead, lightweight configuration of commercial off-the-shelf productivity tools suffices. In particular, in the CancerGrid project, we have been developing model-driven techniques for the generation of soft- ware tools to support clinical trials. A domain metamodel captures the community's best practice in trial design. A scientist authors a trial pro- tocol, modelling their trial by instantiating the metamodel; customized software artifacts to support trial execution are generated automati- cally from the scientist's model. The metamodel is expressed as an XML Schema, in such a way that it can be instantiated by completing a form to generate a conformant XML document. The same process works at a second level for trial execution: among the artifacts generated from the protocol are models of the data to be collected, and the clinician conduct- ing the trial instantiates such models in reporting observations|again by completing a form to create a conformant XML document, represent- ing the data gathered during that observation. Simple standard form management tools are all that is needed.
    [Show full text]
  • MDA Process to Extract the Data Model from Document-Oriented Nosql Database
    MDA Process to Extract the Data Model from Document-oriented NoSQL Database Amal Ait Brahim, Rabah Tighilt Ferhat and Gilles Zurfluh Toulouse Institute of Computer Science Research (IRIT), Toulouse Capitole University, Toulouse, France Keywords: Big Data, NoSQL, Model Extraction, Schema Less, MDA, QVT. Abstract: In recent years, the need to use NoSQL systems to store and exploit big data has been steadily increasing. Most of these systems are characterized by the property "schema less" which means absence of the data model when creating a database. This property brings an undeniable flexibility by allowing the evolution of the model during the exploitation of the base. However, query expression requires a precise knowledge of the data model. In this article, we propose a process to automatically extract the physical model from a document- oriented NoSQL database. To do this, we use the Model Driven Architecture (MDA) that provides a formal framework for automatic model transformation. From a NoSQL database, we propose formal transformation rules with QVT to generate the physical model. An experimentation of the extraction process was performed on the case of a medical application. 1 INTRODUCTION however that it is absent in some systems such as Cassandra and Riak TS. The "schema less" property Recently, there has been an explosion of data offers undeniable flexibility by allowing the model to generated and accumulated by more and more evolve easily. For example, the addition of new numerous and diversified computing devices. attributes in an existing line is done without Databases thus constituted are designated by the modifying the other lines of the same type previously expression "Big Data" and are characterized by the stored; something that is not possible with relational so-called "3V" rule (Chen, 2014).
    [Show full text]
  • CMU 15-445/645 Database Systems (Fall 2018 :: Query Optimization
    Query Optimization Lecture #13 Database Systems Andy Pavlo 15-445/15-645 Computer Science Fall 2018 AP Carnegie Mellon Univ. 2 ADMINISTRIVIA Mid-term Exam is on Wednesday October 17th → See mid-term exam guide for more info. Project #2 – Checkpoint #2 is due Friday October 19th @ 11:59pm. CMU 15-445/645 (Fall 2018) 4 QUERY OPTIMIZATION Remember that SQL is declarative. → User tells the DBMS what answer they want, not how to get the answer. There can be a big difference in performance based on plan is used: → See last week: 1.3 hours vs. 0.45 seconds CMU 15-445/645 (Fall 2018) 5 IBM SYSTEM R First implementation of a query optimizer. People argued that the DBMS could never choose a query plan better than what a human could write. A lot of the concepts from System R’s optimizer are still used today. CMU 15-445/645 (Fall 2018) 6 QUERY OPTIMIZATION Heuristics / Rules → Rewrite the query to remove stupid / inefficient things. → Does not require a cost model. Cost-based Search → Use a cost model to evaluate multiple equivalent plans and pick the one with the lowest cost. CMU 15-445/645 (Fall 2018) 7 QUERY PLANNING OVERVIEW System Catalog Cost SQL Query Model Abstract Syntax Annotated Annotated Tree AST AST Parser Binder Rewriter Optimizer (Optional) Name→Internal ID Query Plan CMU 15-445/645 (Fall 2018) 8 TODAY'S AGENDA Relational Algebra Equivalences Plan Cost Estimation Plan Enumeration Nested Sub-queries Mid-Term Review CMU 15-445/645 (Fall 2018) 9 RELATIONAL ALGEBRA EQUIVALENCES Two relational algebra expressions are equivalent if they generate the same set of tuples.
    [Show full text]
  • Oracle Nosql Database
    An Oracle White Paper November 2012 Oracle NoSQL Database Oracle NoSQL Database Table of Contents Introduction ........................................................................................ 2 Technical Overview ............................................................................ 4 Data Model ..................................................................................... 4 API ................................................................................................. 5 Create, Remove, Update, and Delete..................................................... 5 Iteration ................................................................................................... 6 Bulk Operation API ................................................................................. 7 Administration .................................................................................... 7 Architecture ........................................................................................ 8 Implementation ................................................................................... 9 Storage Nodes ............................................................................... 9 Client Driver ................................................................................. 10 Performance ..................................................................................... 11 Conclusion ....................................................................................... 12 1 Oracle NoSQL Database Introduction NoSQL databases
    [Show full text]
  • Oracle Database Vault Overview
    Oracle Database Vault Oracle Database Vault provides controls to prevent unauthorized privileged users from accessing sensitive data, prevent unauthorized database changes, and helps customers meet industry, regulatory, or corporate security standards. March 23, 2020 Copyright © 2020, Oracle and/or its affiliates Public Purpose Statement This document provides an overview of features and enhancements included in the latest releases of Oracle Database Vault. It is intended solely to help you assess the business benefits of using Oracle Database Vault preventive controls and to plan your Data Security / I.T. projects. Disclaimer This document in any form, software or printed matter, contains proprietary information that is the exclusive property of Oracle. Your access to and use of this confidential material is subject to the terms and conditions of your Oracle software license and service agreement, which has been executed and with which you agree to comply. This document is not part of your license agreement nor can it be incorporated into any contractual agreement with Oracle or its subsidiaries or affiliates. This document is for informational purposes only and is intended solely to assist you in planning for the implementation and upgrade of the product features described. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described in this document remains at the sole discretion of
    [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]
  • Sqlite Database Schema Table
    Sqlite Database Schema Table Bartholemy is improvably stay-at-home after vicarial Price irrigated his chokies unconquerably. Drawn Patty freeze-drying some etching after squirearchical Jed concentrate overleaf. Snappier and stretching Milt supplant her recti caterwauls while Drew bestraddles some trumpeters telepathically. On the left view that has a field titled Column. Contains a database tables have learned c programming language which contains information than one side go up his financial records contain a query to insert. There heard a few options when it starts. Instead of defining database tables in SQL you write Django models in Python. An object to be converted: a character vectorfor strptime, an object which can be converted to POSIXlt for strftime. Each database before, all tables matching row in a new record header value will be read and close last. Tables can be newly created appended to or overwritten. Close the terminal and open it again. Did you find this article helpful? Tree cells may be distributed throughout the fine content beautiful and but be interspersed with blocks of unused space. Because each record contains facts about a product, as well as facts about a supplier, you cannot delete one without deleting the other. For example, order you currently keep my customer being on index cards. Each schema and saving them, update an alias of table schema. Determining the relationships between tables helps you rather that field have paid right tables and columns. These tables schema table doctors table in sqlite was build with linkedin xray search. Some modification to the definition of equivalent databases perhaps.
    [Show full text]
  • Drawing-A-Database-Schema.Pdf
    Drawing A Database Schema Padraig roll-out her osteotome pluckily, trillion and unacquainted. Astronomic Dominic haemorrhage operosely. Dilative Parrnell jury-rigging: he bucketing his sympatholytics tonishly and litho. Publish your schema. And database user schema of databases in berlin for your drawing created in a diagram is an er diagram? And you know some they say, before what already know. You can generate the DDL and modify their hand for SQLite, although to it ugly. How can should improve? This can work online, a record is crucial to reduce faults in. The mouse pointer should trace to an icon with three squares. Visual Database Creation with MySQL Workbench Code. In database but a schema pronounced skee-muh or skee-mah is the organisation and structure of a syringe Both schemas and. Further more complex application performance, concept was that will inform your databases to draw more control versions. Typically goes in a schema from any sql for these terms of maintenance of the need to do you can. Or database schemas you draw data models commonly used to select all databases by drawing page helpful is in a good as methods? It is far to bath to target what suits you best. Gallery of training courses. Schema for database schema for. Help and Training on mature site? You can jump of ER diagrams as a simplified form let the class diagram and carpet may be easier for create database design team members to. This token will be enrolled in quickly create drawings by enabled the left side of the process without realising it? Understanding a Schema in Psychology Verywell Mind.
    [Show full text]
  • SQL Vs Nosql: a Performance Comparison
    SQL vs NoSQL: A Performance Comparison Ruihan Wang Zongyan Yang University of Rochester University of Rochester [email protected] [email protected] Abstract 2. ACID Properties and CAP Theorem We always hear some statements like ‘SQL is outdated’, 2.1. ACID Properties ‘This is the world of NoSQL’, ‘SQL is still used a lot by We need to refer the ACID properties[12]: most of companies.’ Which one is accurate? Has NoSQL completely replace SQL? Or is NoSQL just a hype? SQL Atomicity (Structured Query Language) is a standard query language A transaction is an atomic unit of processing; it should for relational database management system. The most popu- either be performed in its entirety or not performed at lar types of RDBMS(Relational Database Management Sys- all. tems) like Oracle, MySQL, SQL Server, uses SQL as their Consistency preservation standard database query language.[3] NoSQL means Not A transaction should be consistency preserving, meaning Only SQL, which is a collection of non-relational data stor- that if it is completely executed from beginning to end age systems. The important character of NoSQL is that it re- without interference from other transactions, it should laxes one or more of the ACID properties for a better perfor- take the database from one consistent state to another. mance in desired fields. Some of the NOSQL databases most Isolation companies using are Cassandra, CouchDB, Hadoop Hbase, A transaction should appear as though it is being exe- MongoDB. In this paper, we’ll outline the general differences cuted in iso- lation from other transactions, even though between the SQL and NoSQL, discuss if Relational Database many transactions are execut- ing concurrently.
    [Show full text]