Bridge from Entity Relationship modeling to creating SQL databases, tables, & relations
|
|
- Cornelia Park
- 8 years ago
- Views:
Transcription
1 1 Topics for this week: 1. Good Design 2. Functional Dependencies 3. Normalization Readings for this week: 1. E&N, Ch ; Quickstart, Ch Complete the tutorial at In-class Activity: 1. Review components of DBMS, with an eye to viewing the whole process as systematic activities: conceptual, logical, and physical design. 2. Demonstrate by creating a small conceptual and logical model then translating this into part of the physical model - creating the database and tables using MySQL s terminal window. is demonstrates, too, the DDL. 3. Demonstrate a few commands issued against the data (DML). 4. Review some of your ER questions. Bridge from Entity Relationship modeling to creating SQL databases, tables, & relations No doubt, you ve learned already some of the concepts & terminology of relational database modeling. To get up to speed with what you ve covered, here are some quick notes that may help us harmonize our perspectives. Components of a DBMS: Many roles and activities are involved; not all of which you may have encountered. Here s a view of the components of a DBMS. Notice the different contributions of programmers, users, and the DBA - the database administrator. Note, too, the functions that constitute a DBMS (and where the DDL and DML fit in). Ultimately the commands and functions must be communicated to the computer system itself - via the file manager, various other access methods and buffers before reaching the actual data stored in the relationship databases and tables. Query Processor: transforms queries into a series of low-level instructions directed to the database manager. Database Manager (DM): Interacts with the usersubmitted application programs and queries. e DM accepts queries and examines the external and conceptual schema to determine what conceptual records are required to satisfy the request. e DN places a call to the File Manger to perform the request. File Manager: manipulates the underlying storage files and manages the allocation of storage space on the disk. Actual physical manipulation of the data is passed to the appropriate access method. DML preprocessor: converts DML statements embedded in an application program into a
2 2 MySQL). standard function call in the host language (e.g., DDL compiler: compiler converts DDL statements into a set of tables containing meta-data. ese tables are then stored in the catalog while control info is stored in the data files headers. Catalog manager: [not the library kind!] - manages access to and maintains the system catalogue; the system catalog is accessed by most of the DBMS components. ere are other important functions in SQL so ware Terms: Relation: Attribute: Domain a relation is a table with columns & rows an attribute is a named column of a relation is the set of allowable values for one or more attributes. e idea of domain is important because it allows the user to define in a central place the meaning and source of values that attributes can hold. [ is leads to the data dictionary; example below.] Tuple: a tuple is a row of a relation. Degree: the degree of a relation is the number of attributes it contains. Cardinality: the cardinality of a relation is the number of tuples (rows) it contains. As rows are added or deleted, cardinality changes. Relational database is a collection or normalized relations. Example of domains for some branches and staff relations: Attribute Bno Street Area Domain Name BRANCH_NO STREET_NAME AREA_NAME Meaning Domain definition The set of all possible branch characters: size 3, range B1- numbers B99 Set of all streets in Boston character: size 25 Set of all local area names character: size 2
3 3 City Zip and so on... CITY_NAMES ZIP_CODE Names of all towns in Boston Set of zips in Boston character: size 20 character: size 12 Alternative Names: Relation Table File Tuple Row Record Attribute Column Field Now consider the various mathematical combinations from your other readings. ese become important when we consider joins, unions, and other kinds of set operations. Entity-Relationship Modeling ree main items: entity types, relationship types, and attributes. Entity type: an object or concept that is identified by the organization as having an independent existence. Entity: an instance of an entity type that is uniquely identifiable. Weak entity type: an entity type that is existence-dependent on some other entity type. Strong entity type: an entity type that is not existence-dependent on some other entity type. Example: e Staff and Branch items above are strong entities; if there were data about a staff member s next-of-kin, that entity is weak: it exists only if a staff member has a next-of-kin. Attributes are a property of an entity or a relationship type. e Attribute domain is a set of values that may be assigned to that attribute. E.g., Staff->Lname should include only the last names of employees. Some attributes are simple, others composite. A single attribute is composed of a single component with an independent existence. E.g., cannot be further subdivided (e.g., sex, salary; aka atomic attributes ). Composite attributes consist of multiple components; e.g., e Address attribute could be divided into multiple attributes each with their own existence (e.g., street, city, state, zip). Derived attributes are values that are derived from the value of a related attribute or set of attributes, not necessarily in the same entity. For example, paycheck could be derived from hourly_wage * hours_worked. Keys Candidate keys are attributes or sets of attributes that uniquely identify individual occurrences of an entity type. For example, branch number (Bno) is a candidate key for the Branch entity type and has a distinct value for each branch entity. Must be unique for each occurrence (like unique IDs). Primary key is that candidate key selected because of its current and future uniqueness. Composite key is a key consisting of two or more attributes. Diagrammatic Representations Here s an example of Staff, Branch, and Next_of_Kin entities and attributes represented graphically followed by the composition of keys: Staff entity composition: Staff (Staff_No, FName, LName, Address, Tel_No, Sex, DOB, Position, Salary) Primary Key Staff_no Alternate Key FName, LName, DOB Composite Attribute Name (FName, LName) Derived Attribute Total_Staff
4 4 Branch entity type composition: Branch (Branch_No, Street, Area, City, Zip, Tel_No, Fax_No) Primary Key Branch_No Alternate Key Fax_No Composite Attribute Address (Street, Area, City, Zip) Multi-valued Attribute Tel_No Next_of_Kin entity type composition: Next_of_Kin (NName, Address, Tel_No, Relationship) Figure: Diagrammatic representation compare this chart to the above compositions. Other kinds of relationships: Binary, Ternary, Quaternary... (ternary, quaternary are examples of n-ary)
5 5 In addition, there s the issue of recursive relationships and views: Cardinality constraints: Cardinality is the number of possible relationships for each participating entity. e most common degree for relationships is binary and the cardinality ratio for binary relationships are one-to-one (1:1), one-to-many (1:M), and many-to-many (M:N). If the business rule permits it, it is possible to have M:N but with an intervening relationship, e.g., Newspaper [M] ---<advertises> --- [N] Rentals Constraints: Sometimes you can indicate when the relationship participation is mandator and when optional. In addition, you can display the minimum and maximum values (e.g., 5, N) means minimum of 5 instances, no maximum). Problems with ER Models ese problems are called connection traps and occur due to a misinterpretation of the meaning of certain relationships. Two main types: fan traps and chasm traps. In general, to identify connection traps, you must ensure that the meaning of a relationship is fully understood and clearly defined. If not, then the representation doesn t reflect the real world issue. Fan trap: is where a model represents a relationship between entity types, but the pathway between certain entity occurrences is ambiguous. Usually where two or more 1:M relationships fan out from the
6 6 sane entity. Chasm map is where a model suggests the existence of a relationship between entity types, but the pathway does not exist between certain entity occurrences. [ ere are many more traps; there is also the Enhanced Entity Relationship Model (EER). Normalization: to produce a set of relations with desirable properties, given the data requirements of the organization. A main goal is to remove redundancies (although later you ll see there s a time for including redundant data). ere are also many forms of normalization - we ll look at only 1st, 2nd, and 3rd. We want to achieve several goals: (1) to be able to identify uniquely through single or composite keys every datum in the table or sets of tables. (2) e purpose is to avoid anomalies: insertion (when data is added but not in all the right places, e.g., adding new staff but not to the branch where they work); deletion anomalies (same idea but in reverse); modification anomalies (like adding money to your checking account using the ATM but the new balance doesn t reflect the new cash!). Part of the technique of normalization is understanding how data might depend on each others. Functional dependencies: is is a relationship between attributes in a relation. For example, if A and B are attributes of a relation R, B is functionally dependent upon A (denoted A B), if each value of A is associated with exactly one value of B. E.g., Staff_No -- [Position is functionally dependent on Staff_No] --> Position. For example: Staff number S > Manager Fundational dependency is a property of the meaning or semantics of the attributes in a relation. e semantics indicate how attributes relate to one another, and specify the functional dependencies between them. when a functional dependency is present, the dependency is specified as a constraint between them. For example: Let s say B is dependent upon A : if we know the value of A and examine the relationship of the dependency, we find only one value of B in all the rows that have a given value of A. Let s say every staff member has a staff ID # and a job position [S100, Librarian]. at would be represented as StaffNo --> Position. If we know the StaffNo (the data in A), we know the job position (Librarian, the data in B). Conversely we cannot know the data in B (job title = Librarian) unless we know A (StaffNo=S100). [Position attribute is functionally dependent upon Staff_No.] If a person has two job IDs (say login as the department manager or login as the librarian), then then Staff_No is not functionally dependent on Position. [In other words, Jane is the manager and the librarian. She has two ID #s (M5 for manager, S100 for librarian). While knowing staff no. gives us Jane s position, there are many people who are also managers and many who are librarians. Cannot identify uniquely the position. e relationship between Staff_No and Position is 1:1; for each staff number there is only one position. On the other hand, the relationship between Position and Staff_No is 1:M; there are several staff numbers (members of staff) associated with a position. ere is an example of functional dependencies of the Staff_Branch relation [ e ER diagram 2 pages back]. Staff_No --> SName, SAddress, Position, Salary, Branch_no, BAddress, Tel_no Branch_No --> B_Address, Tel_No BAddress -> Branch_No, Tel_No Tel_No --> Branch_No, BAddress Now, to create candidate key(s) for this relation, what attribute or group of attributes uniquely identify each row? Process of normalization: first analyze the relations based on their primary key (or candidate keys) and functional dependencies.
7 7 1st Normal Form (1NF): e intersection of each row and column contains one and only one value. 2nd Normal Form (2NF): A relation that is in first normal form and every non-primary key attribute is fully functionally dependent on the primary key. [Full functional dependency indicates that if A and B are attributes or a relation, B is fully functionally dependent on A if B is functionally dependent on A, but not on any proper subset of A] 3rd NF: A relation that is in first and second normal form and in which no non-primary-key attribute is transitively dependent on the primary key. [Transitive dependence is a condition where A, B, and C are attributes of a relation such that if A B and B C, then C is transitively dependent on A via B (provided that A is not functionally dependent on B or C).] Methodology - Conceptual Database Design. e logic to creating databases has 3 major components: conceptual database design (to build the conceptual representations of the DB, including identification of important entity and relationships); logical database design (to translate the conceptual representation to the logical structure of the database, which includes designing the relations); and Physical database design to allow the designer to decide how the logical structure is to be physically implemented (as tables) on the target database management system. Factors for success in database design: Work interactively with users as much as possible ( Joint Application Design - JAD) Follow a structured methodology throughout the data modeling process Employ a data-driven approach incorporate structural and integrity considerations into the data model Combine conceptual, normalization, and transaction validation techniques into the data modeling methods Use diagrams to represent as much of the data models as possible Use a database design language (DBDL) to represent additional data semantics Build a data dictionary to supplement the data model diagrams Be willing to repeat these steps! Overview of the Database Design Methodology Conceptual DB Design Step 1 Build local conceptual model for each user view 1.1. Identify entity types 1.2. Identify relationship types 1.3. Identify and associate attributes with entity or relationship types 1.4. Determine attribute domains 1.5. Determine candidate and primary key attributes 1.6. Specialize/generalize entity types (optional step) 1.7. Draw ER diagram 1.8. Review local conceptual data model with the user Logical database design for the relationship model Step 2: Build and validate local logical data model for each user view 1.1. Map local conceptual data model to local logical data model 1.2. Derive relations from local logical data model 1.3. Validate model using normalization 1.4. Validate model against user transactions
8 Draw ER diagrams 1.6. Define integrity constraints 1.7. Review local logical data model with user Step 3: Build and validate global logical data model 1.1. Merge local logical data models into a global model 1.2. Validate global logical data model 1.3. Check for future growth 1.4. Draw final ER diagram 1.5. Review with users Physical Database Design Step 4: Translate global local data model for target DBMS 1.1 Design base relations for target DBMS 1.2 Design enterprise constraints for the target DBMS Step 5: Design physical representation 1.1 Analyze transactions 1.2 Choose file organizations 1.3 Choose secondary indices 1.4 Consider the introduction of controlled redundancy 1.5 Estimate disk space requirements Step 6: Design security mechanisms 1.1 Design user views 1.2 Design access rules Step 7: Monitor and tune the operational system * ** * ** * Focusing on the local logical data model (Step 2 above): e goal is to refine the conceptual model to remove undesirable features. 1. Remove M:N relationships: if a M:N is found, try to decompose this relationship to identify an intermediate entry. e M:N relationship becomes two 1:M relationships to the newly identified entity. For example, consider this M:N (Many) newspapers <advertise> (many) rentals. e <advertise> can be decomposed we identify the Advert entity and two new 1:M relationships
9 9 ( Lists and AdvertisesIn Advert (see image): 2. Remove complex relationships 3. Remove recursive relationships 4. Remove relationships with attributes 5. Remove multi-valued relationships 6. Re-examine 1:1 relationships 7. Remove redundant relationships.
Database Design Methodologies
Critical Success Factors in Database Design Database Design Methodologies o Work interactively with the users as much as possible. o Follow a structured methodology throughout the data modeling process.
More information7.1 The Information system
Chapter 7. Database Planning, Design and Administration Last few decades have seen proliferation of software applications, many requiring constant maintenance involving: correcting faults, implementing
More informationDATABASE NORMALIZATION
DATABASE NORMALIZATION Normalization: process of efficiently organizing data in the DB. RELATIONS (attributes grouped together) Accurate representation of data, relationships and constraints. Goal: - Eliminate
More informationNormalization. Purpose of normalization Data redundancy Update anomalies Functional dependency Process of normalization
Normalization Purpose of normalization Data redundancy Update anomalies Functional dependency Process of normalization 1 Purpose of Normalization Normalization is a technique for producing a set of suitable
More informationIT2305 Database Systems I (Compulsory)
Database Systems I (Compulsory) INTRODUCTION This is one of the 4 modules designed for Semester 2 of Bachelor of Information Technology Degree program. CREDITS: 04 LEARNING OUTCOMES On completion of this
More informationLesson 8: Introduction to Databases E-R Data Modeling
Lesson 8: Introduction to Databases E-R Data Modeling Contents Introduction to Databases Abstraction, Schemas, and Views Data Models Database Management System (DBMS) Components Entity Relationship Data
More informationIT2304: Database Systems 1 (DBS 1)
: Database Systems 1 (DBS 1) (Compulsory) 1. OUTLINE OF SYLLABUS Topic Minimum number of hours Introduction to DBMS 07 Relational Data Model 03 Data manipulation using Relational Algebra 06 Data manipulation
More informationDATABASE DESIGN. - Developing database and information systems is performed using a development lifecycle, which consists of a series of steps.
DATABASE DESIGN - The ability to design databases and associated applications is critical to the success of the modern enterprise. - Database design requires understanding both the operational and business
More information2. Conceptual Modeling using the Entity-Relationship Model
ECS-165A WQ 11 15 Contents 2. Conceptual Modeling using the Entity-Relationship Model Basic concepts: entities and entity types, attributes and keys, relationships and relationship types Entity-Relationship
More informationDatabase Design. Marta Jakubowska-Sobczak IT/ADC based on slides prepared by Paula Figueiredo, IT/DB
Marta Jakubowska-Sobczak IT/ADC based on slides prepared by Paula Figueiredo, IT/DB Outline Database concepts Conceptual Design Logical Design Communicating with the RDBMS 2 Some concepts Database: an
More informationDatabase Design Methodology
Topic 7 Database Design Methodology LEARNING OUTCOMES When you have completed this Topic you should be able to: 1. Discuss the purpose of a design methodology. 2. Explain three main phases of design methodology.
More informationnot necessarily strictly sequential feedback loops exist, i.e. may need to revisit earlier stages during a later stage
Database Design Process there are six stages in the design of a database: 1. requirement analysis 2. conceptual database design 3. choice of the DBMS 4. data model mapping 5. physical design 6. implementation
More informationLecture 2 Normalization
MIT 533 ระบบฐานข อม ล 2 Lecture 2 Normalization Walailuk University Lecture 2: Normalization 1 Objectives The purpose of normalization The identification of various types of update anomalies The concept
More informationIntroduction to Computing. Lectured by: Dr. Pham Tran Vu t.v.pham@cse.hcmut.edu.vn
Introduction to Computing Lectured by: Dr. Pham Tran Vu t.v.pham@cse.hcmut.edu.vn Databases The Hierarchy of Data Keys and Attributes The Traditional Approach To Data Management Database A collection of
More informationNormalization. Normalization. Normalization. Data Redundancy
Normalization Normalization o Main objective in developing a logical data model for relational database systems is to create an accurate representation of the data, its relationships, and constraints.
More informationChapter 7 Data Modeling Using the Entity- Relationship (ER) Model
Chapter 7 Data Modeling Using the Entity- Relationship (ER) Model Copyright 2011 Pearson Education, Inc. Publishing as Pearson Addison-Wesley Chapter 7 Outline Using High-Level Conceptual Data Models for
More informationwww.gr8ambitionz.com
Data Base Management Systems (DBMS) Study Material (Objective Type questions with Answers) Shared by Akhil Arora Powered by www. your A to Z competitive exam guide Database Objective type questions Q.1
More informationCSC 742 Database Management Systems
CSC 742 Database Management Systems Topic #4: Data Modeling Spring 2002 CSC 742: DBMS by Dr. Peng Ning 1 Phases of Database Design Requirement Collection/Analysis Functional Requirements Functional Analysis
More information- Eliminating redundant data - Ensuring data dependencies makes sense. ie:- data is stored logically
Normalization of databases Database normalization is a technique of organizing the data in the database. Normalization is a systematic approach of decomposing tables to eliminate data redundancy and undesirable
More informationChapter 3. Data Modeling Using the Entity-Relationship (ER) Model
Chapter 3 Data Modeling Using the Entity-Relationship (ER) Model Chapter Outline Overview of Database Design Process Example Database Application (COMPANY) ER Model Concepts Entities and Attributes Entity
More informationLecture 6. SQL, Logical DB Design
Lecture 6 SQL, Logical DB Design Relational Query Languages A major strength of the relational model: supports simple, powerful querying of data. Queries can be written intuitively, and the DBMS is responsible
More informationRelational Schema Design
Relational Schema Design Using ER Methodology to Design Relational Database Schemas The Development Process Collect requirements. Analyze the requirements. Conceptually design the data (e.g., draw an ER
More informationUnit 2.1. Data Analysis 1 - V2.0 1. Data Analysis 1. Dr Gordon Russell, Copyright @ Napier University
Data Analysis 1 Unit 2.1 Data Analysis 1 - V2.0 1 Entity Relationship Modelling Overview Database Analysis Life Cycle Components of an Entity Relationship Diagram What is a relationship? Entities, attributes,
More informationIntroduction to normalization. Introduction to normalization
Introduction to normalization Lecture 4 Instructor Anna Sidorova Agenda Presentation Review of relational models, in class exersise Introduction to normalization In-class exercises Discussion of HW2 1
More informationData Analysis 1. SET08104 Database Systems. Copyright @ Napier University
Data Analysis 1 SET08104 Database Systems Copyright @ Napier University Entity Relationship Modelling Overview Database Analysis Life Cycle Components of an Entity Relationship Diagram What is a relationship?
More informationBCA. Database Management System
BCA IV Sem Database Management System Multiple choice questions 1. A Database Management System (DBMS) is A. Collection of interrelated data B. Collection of programs to access data C. Collection of data
More informationTHE ENTITY- RELATIONSHIP (ER) MODEL CHAPTER 7 (6/E) CHAPTER 3 (5/E)
THE ENTITY- RELATIONSHIP (ER) MODEL CHAPTER 7 (6/E) CHAPTER 3 (5/E) 2 LECTURE OUTLINE Using High-Level, Conceptual Data Models for Database Design Entity-Relationship (ER) model Popular high-level conceptual
More informationThe Relational Model. Ramakrishnan&Gehrke, Chapter 3 CS4320 1
The Relational Model Ramakrishnan&Gehrke, Chapter 3 CS4320 1 Why Study the Relational Model? Most widely used model. Vendors: IBM, Informix, Microsoft, Oracle, Sybase, etc. Legacy systems in older models
More information1 File Processing Systems
COMP 378 Database Systems Notes for Chapter 1 of Database System Concepts Introduction A database management system (DBMS) is a collection of data and an integrated set of programs that access that data.
More informationDesigning a Database Schema
Week 10: Database Design Database Design From an ER Schema to a Relational One Restructuring an ER schema Performance Analysis Analysis of Redundancies, Removing Generalizations Translation into a Relational
More informationDatabases What the Specification Says
Databases What the Specification Says Describe flat files and relational databases, explaining the differences between them; Design a simple relational database to the third normal form (3NF), using entityrelationship
More information14 Databases. Source: Foundations of Computer Science Cengage Learning. Objectives After studying this chapter, the student should be able to:
14 Databases 14.1 Source: Foundations of Computer Science Cengage Learning Objectives After studying this chapter, the student should be able to: Define a database and a database management system (DBMS)
More informationCOMP 378 Database Systems Notes for Chapter 7 of Database System Concepts Database Design and the Entity-Relationship Model
COMP 378 Database Systems Notes for Chapter 7 of Database System Concepts Database Design and the Entity-Relationship Model The entity-relationship (E-R) model is a a data model in which information stored
More informationDatabase Concepts. Database & Database Management System. Application examples. Application examples
Database & Database Management System Database Concepts Database = A shared collection of logically related (and a description of this data), designed to meet the information needs of an organization.
More informationFundamentals of Database Design
Fundamentals of Database Design Zornitsa Zaharieva CERN Data Management Section - Controls Group Accelerators and Beams Department /AB-CO-DM/ 23-FEB-2005 Contents : Introduction to Databases : Main Database
More informationEntity-Relationship Model
UNIT -2 Entity-Relationship Model Introduction to ER Model ER model is represents real world situations using concepts, which are commonly used by people. It allows defining a representation of the real
More informationæ A collection of interrelated and persistent data èusually referred to as the database èdbèè.
CMPT-354-Han-95.3 Lecture Notes September 10, 1995 Chapter 1 Introduction 1.0 Database Management Systems 1. A database management system èdbmsè, or simply a database system èdbsè, consists of æ A collection
More informationDATABASE DESIGN: NORMALIZATION NOTE & EXERCISES (Up to 3NF)
DATABASE DESIGN: NORMALIZATION NOTE & EXERCISES (Up to 3NF) Tables that contain redundant data can suffer from update anomalies, which can introduce inconsistencies into a database. The rules associated
More informationConceptual Design Using the Entity-Relationship (ER) Model
Conceptual Design Using the Entity-Relationship (ER) Model Module 5, Lectures 1 and 2 Database Management Systems, R. Ramakrishnan 1 Overview of Database Design Conceptual design: (ER Model is used at
More informationChapter 3. Database Environment - Objectives. Multi-user DBMS Architectures. Teleprocessing. File-Server
Chapter 3 Database Architectures and the Web Transparencies Database Environment - Objectives The meaning of the client server architecture and the advantages of this type of architecture for a DBMS. The
More informationPart 2 - The Database Environment
Rela%onal Database 2 1 Part 2 - The Database Environment The purpose of a RDBMS is to provide users with an abstract view of the data, hiding certain details of how data are stored and manipulated. Therefore,
More informationThe Relational Model. Why Study the Relational Model? Relational Database: Definitions. Chapter 3
The Relational Model Chapter 3 Database Management Systems 3ed, R. Ramakrishnan and J. Gehrke 1 Why Study the Relational Model? Most widely used model. Vendors: IBM, Informix, Microsoft, Oracle, Sybase,
More informationFoundations of Information Management
Foundations of Information Management - WS 2012/13 - Juniorprofessor Alexander Markowetz Bonn Aachen International Center for Information Technology (B-IT) Data & Databases Data: Simple information Database:
More informationInformation Systems Analysis and Design CSC340. 2004 John Mylopoulos Database Design -- 2. Information Systems Analysis and Design CSC340
XX. Database Design Databases Databases and DBMS Data Models, Hierarchical, Network, Relational Database Design Restructuring an ER schema Performance analysis Analysis of Redundancies, Removing generalizations
More informationCS2Bh: Current Technologies. Introduction to XML and Relational Databases. Introduction to Databases. Why databases? Why not use XML?
CS2Bh: Current Technologies Introduction to XML and Relational Databases Spring 2005 Introduction to Databases CS2 Spring 2005 (LN5) 1 Why databases? Why not use XML? What is missing from XML: Consistency
More informationChapter 1: Introduction
Chapter 1: Introduction Purpose of Database Systems View of Data Data Models Data Definition Language Data Manipulation Language Transaction Management Storage Management Database Administrator Database
More informationChapter 2 Database System Concepts and Architecture
Chapter 2 Database System Concepts and Architecture Copyright 2011 Pearson Education, Inc. Publishing as Pearson Addison-Wesley Chapter 2 Outline Data Models, Schemas, and Instances Three-Schema Architecture
More informationDatabases and BigData
Eduardo Cunha de Almeida eduardo.almeida@uni.lu Outline of the course Introduction Database Systems (E. Almeida) Distributed Hash Tables and P2P (C. Cassagnes) NewSQL (D. Kim and J. Meira) NoSQL (D. Kim)
More informationDATABASE INTRODUCTION
Introduction The history of database system research is one of exceptional productivity and startling economic impact. We have learnt that from the days of file-based systems there are better ways to handle
More informationA brief overview of developing a conceptual data model as the first step in creating a relational database.
Data Modeling Windows Enterprise Support Database Services provides the following documentation about relational database design, the relational database model, and relational database software. Introduction
More informationIntroduction to Databases
Page 1 of 5 Introduction to Databases An introductory example What is a database? Why do we need Database Management Systems? The three levels of data abstraction What is a Database Management System?
More informationChapter 1: Introduction. Database Management System (DBMS) University Database Example
This image cannot currently be displayed. Chapter 1: Introduction Database System Concepts, 6 th Ed. See www.db-book.com for conditions on re-use Database Management System (DBMS) DBMS contains information
More informationLecture Notes INFORMATION RESOURCES
Vilnius Gediminas Technical University Jelena Mamčenko Lecture Notes on INFORMATION RESOURCES Part I Introduction to Dta Modeling and MSAccess Code FMITB02004 Course title Information Resourses Course
More informationDATABASE MANAGEMENT SYSTEMS. Question Bank:
DATABASE MANAGEMENT SYSTEMS Question Bank: UNIT 1 1. Define Database? 2. What is a DBMS? 3. What is the need for database systems? 4. Define tupule? 5. What are the responsibilities of DBA? 6. Define schema?
More informationDatabase Fundamentals: 1
Database Fundamentals Robert J. Robbins Johns Hopkins University rrobbins@gdb.org Database Fundamentals: 1 What is a Database? General: A database is any collection of related data. Restrictive: A database
More informationDatabase Management Systems. Chapter 1
Database Management Systems Chapter 1 Database Management Systems 3ed, R. Ramakrishnan and J. Gehrke 2 What Is a Database/DBMS? A very large, integrated collection of data. Models real-world scenarios
More informationDatabase Systems Introduction Dr P Sreenivasa Kumar
Database Systems Introduction Dr P Sreenivasa Kumar Professor CS&E Department I I T Madras 1 Introduction What is a Database? A collection of related pieces of data: Representing/capturing the information
More informationLecture #11 Relational Database Systems KTH ROYAL INSTITUTE OF TECHNOLOGY
Lecture #11 Relational Database Systems KTH ROYAL INSTITUTE OF TECHNOLOGY Contents Storing data Relational Database Systems Entity Relationship diagrams Normalisation of ER diagrams Tuple Relational Calculus
More informationDatabase Design Methodology
Database Design Methodology Three phases Database Design Methodology Logical database Physical database Constructing a model of the information used in an enterprise on a specific data model but independent
More informationGUJARAT TECHNOLOGICAL UNIVERSITY, AHMEDABAD, GUJARAT. COURSE CURRICULUM COURSE TITLE: DATABASE MANAGEMENT (Code: 3341605 ) Information Technology
GUJARAT TECHNOLOGICAL UNIVERSITY, AHMEDABAD, GUJARAT COURSE CURRICULUM COURSE TITLE: DATABASE MANAGEMENT (Code: 3341605 ) Diploma Programme in which this course is offered Information Technology Semester
More informationRelational model. Relational model - practice. Relational Database Definitions 9/27/11. Relational model. Relational Database: Terminology
COS 597A: Principles of Database and Information Systems elational model elational model A formal (mathematical) model to represent objects (data/information), relationships between objects Constraints
More informationOutline. Data Modeling. Conceptual Design. ER Model Basics: Entities. ER Model Basics: Relationships. Ternary Relationships. Yanlei Diao UMass Amherst
Outline Data Modeling Yanlei Diao UMass Amherst v Conceptual Design: ER Model v Relational Model v Logical Design: from ER to Relational Slides Courtesy of R. Ramakrishnan and J. Gehrke 1 2 Conceptual
More informationDBMS / Business Intelligence, SQL Server
DBMS / Business Intelligence, SQL Server Orsys, with 30 years of experience, is providing high quality, independant State of the Art seminars and hands-on courses corresponding to the needs of IT professionals.
More informationThe process of database development. Logical model: relational DBMS. Relation
The process of database development Reality (Universe of Discourse) Relational Databases and SQL Basic Concepts The 3rd normal form Structured Query Language (SQL) Conceptual model (e.g. Entity-Relationship
More informationBasic Concepts of Database Systems
CS2501 Topic 1: Basic Concepts 1.1 Basic Concepts of Database Systems Example Uses of Database Systems - account maintenance & access in banking - lending library systems - airline reservation systems
More informationReview: Participation Constraints
Review: Participation Constraints Does every department have a manager? If so, this is a participation constraint: the participation of Departments in Manages is said to be total (vs. partial). Every did
More informationDatabase Management Systems
Database Management Systems Database Design (1) 1 Topics Information Systems Life Cycle Data Base Design Logical Design Physical Design Entity Relationship (ER) Model Entity Relationship Attributes Cardinality
More informationDBMS Questions. 3.) For which two constraints are indexes created when the constraint is added?
DBMS Questions 1.) Which type of file is part of the Oracle database? A.) B.) C.) D.) Control file Password file Parameter files Archived log files 2.) Which statements are use to UNLOCK the user? A.)
More informationDatabases Model the Real World. The Entity- Relationship Model. Conceptual Design. Steps in Database Design. ER Model Basics. ER Model Basics (Contd.
The Entity- Relationship Model R &G - Chapter 2 A relationship, I think, is like a shark, you know? It has to constantly move forward or it dies. And I think what we got on our hands is a dead shark. Woody
More informationDatabase Management. Technology Briefing. Modern organizations are said to be drowning in data but starving for information p.
Technology Briefing Database Management Modern organizations are said to be drowning in data but starving for information p. 509 TB3-1 Learning Objectives TB3-2 Learning Objectives TB3-3 Database Management
More informationLOGICAL DATABASE DESIGN
MODULE 8 LOGICAL DATABASE DESIGN OBJECTIVE QUESTIONS There are 4 alternative answers to each question. One of them is correct. Pick the correct answer. Do not guess. A key is given at the end of the module
More informationRelational Database Basics Review
Relational Database Basics Review IT 4153 Advanced Database J.G. Zheng Spring 2012 Overview Database approach Database system Relational model Database development 2 File Processing Approaches Based on
More informationFiles. Files. Files. Files. Files. File Organisation. What s it all about? What s in a file?
Files What s it all about? Information being stored about anything important to the business/individual keeping the files. The simple concepts used in the operation of manual files are often a good guide
More informationDatabase IST400/600. Jian Qin. A collection of data? A computer system? Everything you collected for your group project?
Relational Databases IST400/600 Jian Qin Database A collection of data? Everything you collected for your group project? A computer system? File? Spreadsheet? Information system? Date s criteria: Integration
More informationIV. The (Extended) Entity-Relationship Model
IV. The (Extended) Entity-Relationship Model The Extended Entity-Relationship (EER) Model Entities, Relationships and Attributes Cardinalities, Identifiers and Generalization Documentation of EER Diagrams
More informationChapter 1: Introduction
Chapter 1: Introduction Database System Concepts, 5th Ed. See www.db book.com for conditions on re use Chapter 1: Introduction Purpose of Database Systems View of Data Database Languages Relational Databases
More informationWhat is a database? COSC 304 Introduction to Database Systems. Database Introduction. Example Problem. Databases in the Real-World
COSC 304 Introduction to Systems Introduction Dr. Ramon Lawrence University of British Columbia Okanagan ramon.lawrence@ubc.ca What is a database? A database is a collection of logically related data for
More informationChapter 1: Introduction. Database Management System (DBMS)
Chapter 1: Introduction Purpose of Database Systems View of Data Data Models Data Definition Language Data Manipulation Language Transaction Management Storage Management Database Administrator Database
More information2. Basic Relational Data Model
2. Basic Relational Data Model 2.1 Introduction Basic concepts of information models, their realisation in databases comprising data objects and object relationships, and their management by DBMS s that
More informationHow To Write A Diagram
Data Model ing Essentials Third Edition Graeme C. Simsion and Graham C. Witt MORGAN KAUFMANN PUBLISHERS AN IMPRINT OF ELSEVIER AMSTERDAM BOSTON LONDON NEW YORK OXFORD PARIS SAN DIEGO SAN FRANCISCO SINGAPORE
More informationConcepts of Database Management Seventh Edition. Chapter 6 Database Design 2: Design Method
Concepts of Database Management Seventh Edition Chapter 6 Database Design 2: Design Method Objectives Discuss the general process and goals of database design Define user views and explain their function
More informationData Modeling Basics
Information Technology Standard Commonwealth of Pennsylvania Governor's Office of Administration/Office for Information Technology STD Number: STD-INF003B STD Title: Data Modeling Basics Issued by: Deputy
More informationStudy Notes for DB Design and Management Exam 1 (Chapters 1-2-3) record A collection of related (logically connected) fields.
Study Notes for DB Design and Management Exam 1 (Chapters 1-2-3) Chapter 1 Glossary Table data Raw facts; that is, facts that have not yet been processed to reveal their meaning to the end user. field
More informationModern Systems Analysis and Design
Modern Systems Analysis and Design Prof. David Gadish Structuring System Data Requirements Learning Objectives Concisely define each of the following key data modeling terms: entity type, attribute, multivalued
More informationChapter 10. Practical Database Design Methodology. The Role of Information Systems in Organizations. Practical Database Design Methodology
Chapter 10 Practical Database Design Methodology Practical Database Design Methodology Design methodology Target database managed by some type of database management system Various design methodologies
More informationFundamentals of Database System
Fundamentals of Database System Chapter 4 Normalization Fundamentals of Database Systems (Chapter 4) Page 1 Introduction To Normalization In general, the goal of a relational database design is to generate
More informationAbout the Tutorial. Audience. Prerequisites. Copyright & Disclaimer
About the Tutorial Database Management System or DBMS in short refers to the technology of storing and retrieving users data with utmost efficiency along with appropriate security measures. DBMS allows
More informationInstant SQL Programming
Instant SQL Programming Joe Celko Wrox Press Ltd. INSTANT Table of Contents Introduction 1 What Can SQL Do for Me? 2 Who Should Use This Book? 2 How To Use This Book 3 What You Should Know 3 Conventions
More informationThe Entity-Relationship Model
The Entity-Relationship Model Overview of Database Design Requirements analysis Conceptual design data model Logical design Schema refinement: Normalization Physical tuning Conceptual Design Entities Conceptual
More informationISM 318: Database Systems. Objectives. Database. Dr. Hamid R. Nemati
ISM 318: Database Systems Dr. Hamid R. Nemati Department of Information Systems Operations Management Bryan School of Business Economics Objectives Underst the basics of data databases Underst characteristics
More informationInformation Systems SQL. Nikolaj Popov
Information Systems SQL Nikolaj Popov Research Institute for Symbolic Computation Johannes Kepler University of Linz, Austria popov@risc.uni-linz.ac.at Outline SQL Table Creation Populating and Modifying
More informationBasic and Advanced Database Courses
Basic and Advanced Database Courses Srdjan Škrbić Faculty of Science, University of Novi Sad Trg Dositeja Obradovića 4, 21000 Novi Sad, Serbia shkrba@uns.ac.rs http://www.is.pmf.uns.ac.rs/skrbics At the
More informationNormalization in Database Design
in Database Design Marek Rychly mrychly@strathmore.edu Strathmore University, @ilabafrica & Brno University of Technology, Faculty of Information Technology Advanced Databases and Enterprise Systems 14
More informationChapter 2: Entity-Relationship Model. Entity Sets. " Example: specific person, company, event, plant
Chapter 2: Entity-Relationship Model! Entity Sets! Relationship Sets! Design Issues! Mapping Constraints! Keys! E-R Diagram! Extended E-R Features! Design of an E-R Database Schema! Reduction of an E-R
More informationChapter 2. Data Model. Database Systems: Design, Implementation, and Management, Sixth Edition, Rob and Coronel
Chapter 2 Data Model Database Systems: Design, Implementation, and Management, Sixth Edition, Rob and Coronel 1 In this chapter, you will learn: Why data models are important About the basic data-modeling
More information1. INTRODUCTION TO RDBMS
Oracle For Beginners Page: 1 1. INTRODUCTION TO RDBMS What is DBMS? Data Models Relational database management system (RDBMS) Relational Algebra Structured query language (SQL) What Is DBMS? Data is one
More informationA Tool for Generating Relational Database Schema from EER Diagram
A Tool for Generating Relational Schema from EER Diagram Lisa Simasatitkul and Taratip Suwannasart Abstract design is an important activity in software development. EER diagram is one of diagrams, which
More informationA. TRUE-FALSE: GROUP 2 PRACTICE EXAMPLES FOR THE REVIEW QUIZ:
GROUP 2 PRACTICE EXAMPLES FOR THE REVIEW QUIZ: Review Quiz will contain very similar question as below. Some questions may even be repeated. The order of the questions are random and are not in order of
More informationDatabase System Concepts
s Design Chapter 1: Introduction Departamento de Engenharia Informática Instituto Superior Técnico 1 st Semester 2008/2009 Slides (fortemente) baseados nos slides oficiais do livro c Silberschatz, Korth
More informationVALLIAMMAI ENGNIEERING COLLEGE SRM Nagar, Kattankulathur 603203.
VALLIAMMAI ENGNIEERING COLLEGE SRM Nagar, Kattankulathur 603203. DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING Year & Semester : II / III Section : CSE - 1 & 2 Subject Code : CS 6302 Subject Name : Database
More information