Announcements Informatics major Information session tomorrow 12:30-1:30 in MGH 420 Informatics video 12/15/2015D.A. Clements, MLIS, UW iSchool 1.

Slides:



Advertisements
Similar presentations
CHAPTER OBJECTIVE: NORMALIZATION THE SNOWFLAKE SCHEMA.
Advertisements

Chapter 15 A Table with a View: Database Queries.
Database Management System MIS 520 – Database Theory Fall 2001 (Day) Lecture 13.
Management Information Systems, Sixth Edition
Relational Databases Chapter 4.
Databases.
Oct 31, 2000Database Management -- Fall R. Larson Database Management: Introduction to Terms and Concepts University of California, Berkeley School.
CSCI 150 Database Applications Chapter 1 – Getting Started.
Chapter 4 Relational Databases Copyright © 2012 Pearson Education, Inc. publishing as Prentice Hall 4-1.
Database Design Overview. 2 Database DBMS File Record Field Cardinality Keys Index Pointer Referential Integrity Normalization Data Definition Language.
Chapter 4 Relational Databases Copyright © 2012 Pearson Education 4-1.
Chapter 15 Introduction to Database Concepts. Copyright © 2013 Pearson Education, Inc. Publishing as Pearson Addison-Wesley Learning Objectives Explain.
1 Access Lesson 3 Creating Queries Microsoft Office 2010 Introductory.
Chapter 5 Database Processing.
COMPUTING FOR BUSINESS AND ECONOMICS-III. Lecture no.6 COURSE INSTRUCTOR- Ms. Tehseen SEMESTER- Summer 2010.
Database Design Concepts
1 DATABASE TECHNOLOGIES BUS Abdou Illia, Fall 2007 (Week 3, Tuesday 9/4/2007)
© Paradigm Publishing Inc. 9-1 Chapter 9 Database and Information Management.
Chapter 1 Overview of Database Concepts Oracle 10g: SQL
Database Technical Session By: Prof. Adarsh Patel.
Fluency with Information Technology INFO100 and CSE100 Katherine Deibel Katherine Deibel, Fluency in Information Technology1.
Microsoft Access 2003 Define some key Access terminology: Field – A single characteristic or attribute of a person, place, object, event, or idea. Record.
CHAPTER 8: MANAGING DATA RESOURCES. File Organization Terms Field: group of characters that represent something Record: group of related fields File:
MIS 301 Information Systems in Organizations Dave Salisbury ( )
Lecture 2 An Overview of Relational Database IST 318 – DB Admin.
RELATIONSHIPS Generally there are two main database types: flat-file and relational.
I Information Systems Technology Ross Malaga 4 "Part I Understanding Information Systems Technology" Copyright © 2005 Prentice Hall, Inc. 4-1 DATABASE.
Copyright © Curt Hill The Relational Model of Database Basic organization and terms.
Storing Organizational Information - Databases
Information Systems & Databases 2.2) Organisation methods.
MIS 327 Database Management system 1 MIS 327: DBMS Dr. Monther Tarawneh Dr. Monther Tarawneh Week 2: Basic Concepts.
DataBase Management System What is DBMS Purpose of DBMS Data Abstraction Data Definition Language Data Manipulation Language Data Models Data Keys Relationships.
Databases Shortfalls of file management systems Structure of a database Database administration Database Management system Hierarchical Databases Network.
INFO1408 Database Design Concepts Week 15: Introduction to Database Management Systems.
Prepared By Prepared By : VINAY ALEXANDER ( विनय अलेक्सजेंड़र ) PGT(CS),KV JHAGRAKHAND.
Advanced Accounting Information Systems Day 7 Database Modeling.
Chapter 13 Designing Databases Systems Analysis and Design Kendall & Kendall Sixth Edition.
Database Fundamentals CSC105 Furman University Peggy Batchelor.
Relational Theory and Design
Creating DDL and Database Event Triggers. 2 home back first prev next last What Will I Learn? Describe events that cause DDL and database event triggers.
Copyright © 2008 Pearson Education, Inc. Publishing as Pearson Addison-Wesley Fluency with Information Technology Third Edition by Lawrence Snyder Chapter.
Programming Logic and Design Fourth Edition, Comprehensive Chapter 16 Using Relational Databases.
Database Management Supplement 1. 2 I. The Hierarchy of Data Database File (Entity, Table) Record (info for a specific entity, Row) Field (Attribute,
Foundations of Business Intelligence: Databases and Information Management.
Announcements CLUE Tutoring Wednesday nights 7-8:30PM MGH extra-credit points for each session you attend from last week through the end of the quarter.
IS 320 Notes for April 15, Learning Objectives Understand database concepts. Use normalization to efficiently store data in a database. Use.
1 DATABASE TECHNOLOGIES (Part 2) BUS Abdou Illia, Fall 2015 (September 9, 2015)
1 Announcements Project Due Friday 5:00 PM Group Presentations –10 minutes –Describe project (ERD), discuss any challenges, show us some queries Final.
Copyright © 2009 Pearson Education, Inc. Publishing as Prentice Hall Chapter 9 Designing Databases 9.1.
Understand Primary, Foreign, and Composite Keys Database Administration Fundamentals LESSON 4.2.
* Database is a group of related objects * Objects can be Tables, Forms, Queries or Reports * All data reside in Tables * A Row in a Table is a record.
Fluency with Information Technology INFO100 and CSE100 Katherine Deibel Katherine Deibel, Fluency in Information Technology1.
6.1 © 2007 by Prentice Hall Chapter 6 (Laudon & Laudon) Foundations of Business Intelligence: Databases and Information Management.
Howard Paul. Sequential Access Index Files and Data File Random Access.
Test Your Tech Navigation is: A. Following a series of links to locate specific information on the Web. B. Finding your uncle's mountain cabin in dense.
Teanna Clarke 6aQ What is a Entity-Relationship Diagram?  An Entity-Relationship Diagram (ERD) is a tool that graphically shows the connections among.
Management Information Systems by Prof. Park Kyung-Hye Chapter 7 (8th Week) Databases and Data Warehouses 07.
DBM 380 AID Focus Dreams/dbm380aid.com
Divisibility Rules.
A Table with a View: Database Queries
Chapter 4 Relational Databases
Database Structure Chapter 16.
Databases and Information Management
Basic Concepts in Data Management
D.A. Clements, UW Information School
Announcements Project 2’s due date is moved to Tuesday 8/3/04
Test Your Tech Blogging is: Someone's online journal.
A Table with a View: Database Queries
Divisibility Rules.
A Table with a View: Database Queries
Presentation transcript:

Announcements Informatics major Information session tomorrow 12:30-1:30 in MGH 420 Informatics video 12/15/2015D.A. Clements, MLIS, UW iSchool 1

Announcements Due Friday at 10pm Vote for the Best GoPosters WebQ 5 points XC for everyone who answers Ten winners will also receive points XC Weekly GoPost discussion 12/15/2015D.A. Clements, MLIS, UW iSchool 2

Announcements Quiz in lab on Wednesday/Thursday Topics on GoPost 12/15/2015D.A. Clements, MLIS, UW iSchool 3

Database Tables, Views, and Design D.A. Clements 12/15/ D.A. Clements, MLIS, UW iSchool

TABLES AND VIEWS Physical and Logical Database 12/15/ D.A. Clements, MLIS, UW iSchool

Structure of a Database Physical database and logical database Physical database is the files, records in any order, no logical organization other than tables Logical database is a view of database that shows only the rows and fields needed by the users Solves Information Overload and Security: Users see only what they need Users see only what they have permission to see D.A. Clements, MLIS, UW iSchool12/15/2015

Physical vs. Logical /15/2015D.A. Clements, MLIS, UW iSchool

16-8 Physical Database Designed by database administrators Fast to access No redundancy/duplicating information Multiple data can lead to inconsistent data Backup copies in case of accidental data deletion or disk crash 12/15/2015D.A. Clements, MLIS, UW iSchool

16-9 Logical Database Creating specialized views of the data for different users' needs Creating a new “result set” from the current data each time Fresh Accurate 12/15/2015D.A. Clements, MLIS, UW iSchool

16-10 Defining Physical Tables Database schemes (schema) Metadata specification that describes the database design 12/15/2015D.A. Clements, MLIS, UW iSchool

/15/2015D.A. Clements, MLIS, UW iSchool

16-12 The Idea of Relationship A relationship is a correspondence between rows of one table and the rows of another table key Student_ID is used in each table, Find address for each student (Lives_At) Find the student for each address (Home_Of) Relationship examples 12/15/2015D.A. Clements, MLIS, UW iSchool

16-13 Relationships in Practice 12/15/2015D.A. Clements, MLIS, UW iSchool

16-14 Defining Logical Tables Constructing a View Using Join Match on the common field of Student_ID Master_List = Student JOIN Home_Base On Student.Student_ID = Home_Base.Student_ID 12/15/2015D.A. Clements, MLIS, UW iSchool

Designing a Database Hands on in Access and on paper 15 min. 12/15/ D.A. Clements, MLIS, UW iSchool

Athletes and Teams “Business Rules” What the database is about What things are important How things relate 12/15/ D.A. Clements, MLIS, UW iSchool

Athletes and Teams A Database for an athletics department at a high school Storing details of: Teams with division, gender, coach Student Athletes Individuals are selected for a team. Keep track of the points awarded to each student for participating in a sport for the awarding of school letters. The Database has to keep track of student Athletes over five years with any given Athlete participating in multiple sports in a given year. 12/15/ D.A. Clements, MLIS, UW iSchool

Athletes and Teams THINGS of Interest, include : Athletes Events Points earned for success Teams These THINGS are related as follows: A Student Athlete can participate in zero, one or many TEAMS. 12/15/ D.A. Clements, MLIS, UW iSchool

Athletes and Teams student_id student_result_at_event student_points_to_date student_points_at_event student_first_name letters_sport_code student_middle_name letters_awarded_date student_last_name team_gender student_date_of_birth event_location team_name student_gender team_description student_address coach_name student_other_details team_other_details division_description sport_description event_name event_start_date event_end_date event_other_details 12/15/ D.A. Clements, MLIS, UW iSchool

Design the Database Divide into teams of three or four: Design the Students and Teams database: Decide what tables you would build. Decide what fields you would put in each table. List table names and attributes. Choose primary keys. List foreign keys in the foreign table. You have 15 minutes 12/15/ D.A. Clements, MLIS, UW iSchool