Practical Database Design



Similar documents
Database Design Basics


Microsoft Access Part I (Database Design Basics) ShortCourse Handout

Microsoft Access Basics

Microsoft Access 2003 Module 1

Access Tutorial 2 Building a Database and Defining Table Relationships

ISM 318: Database Systems. Objectives. Database. Dr. Hamid R. Nemati

Introduction to Microsoft Access 2003

Consider the possible problems with storing the following data in a spreadsheet:

Microsoft Access 2007 Module 1

Filter by Selection button. Displays records by degree to which they match the selected record. Click to view advanced filtering options

INTRODUCTION TO MICROSOFT ACCESS Tables, Queries, Forms & Reports

- Suresh Khanal. Microsoft Excel Short Questions and Answers 1

12 File and Database Concepts 13 File and Database Concepts A many-to-many relationship means that one record in a particular record type can be relat

User Services. Intermediate Microsoft Access. Use the new Microsoft Access. Getting Help. Instructors OBJECTIVES. July 2009

Information Technology Services Kennesaw State University

Tutorial on Relational Database Design

Access Part 2 - Design

CHAPTER 6 DATABASE MANAGEMENT SYSTEMS. Learning Objectives

Reduced Quality Sample

Technology in Action. Alan Evans Kendall Martin Mary Anne Poatsy. Eleventh Edition. Copyright 2015 Pearson Education, Inc.

Access Database Design

Microsoft Using an Existing Database Amarillo College Revision Date: July 30, 2008

Getting Started with Access 2007

What is a database? The parts of an Access database

DESKTOP PRODUCTIVITY SOFTWARE

User Services. Microsoft Access 2003 II. Use the new Microsoft

Once the schema has been designed, it can be implemented in the RDBMS.

EUROPEAN COMPUTER DRIVING LICENCE. Module AM5, Database, Advanced-Level

Using an Access Database

Course Title: Microsoft Access Basic Duration: 12 hours

4 Steps to Select a Fixed Asset Management & Depreciation Solution

Managing Databases minutes. Teacher Notes: Jorge Viegas B.Sci.(Chemical), Dip.Ed.,Associate Dip in Lab Technology

A Basic introduction to Microsoft Access

Introduction to Computing. Lectured by: Dr. Pham Tran Vu

Credit value: 10 Guided learning hours: 60

Using Excel As A Database

Use Find & Replace Commands under Home tab to search and replace data.

BUS Business Computer Lab Course Outline Fall Term 2015 Section 001 Wednesday, 11:30-12:45, ED531

Databases with Microsoft Access. Using Access to create Databases Jan-Feb 2003

Microsoft Access Glossary of Terms

CHAPTER 6: ANALYZE MICROSOFT DYNAMICS NAV 5.0 DATA IN MICROSOFT EXCEL

Normalization. Reduces the liklihood of anomolies

MODULE 2: SMARTLIST, REPORTS AND INQUIRIES

4. The Third Stage In Designing A Database Is When We Analyze Our Tables More Closely And Create A Between Tables

PROJECT ON MICROSOFT ACCESS (HOME TAB AND EXTERNAL DATA TAB) SUBMITTED BY: SUBMITTED TO: NAME: ROLL NO: REGN NO: BATCH:

Bridge from Entity Relationship modeling to creating SQL databases, tables, & relations

Access Creating Databases - Fundamentals

1. INTRODUCTION TO RDBMS

Microsoft Office 2010: Access 2010, Excel 2010, Lync 2010 learning assets

Creating tables in Microsoft Access 2007

Creating and Using Databases with Microsoft Access

Creating a Participants Mailing and/or Contact List:

How To Create A Report In Excel

INFO Koffka Khan. Tutorial 6

Physical Database Design Process. Physical Database Design Process. Major Inputs to Physical Database. Components of Physical Database Design

Topics. Database Essential Concepts. What s s a Good Database System? Using Database Software. Using Database Software. Types of Database Programs

Vector HelpDesk - Administrator s Guide

Administering a Microsoft SQL Server 2000 Database

Adam Rauch Partner, LabKey Software Extending LabKey Server Part 1: Retrieving and Presenting Data

Database Applications Microsoft Access

INTRODUCTION TO MICROSOFT ACCESS MINIMAL MANUAL

Advanced Excel Charts : Tables : Pivots : Macros

z Introduction to Relational Databases for Clinical Research Michael A. Kohn, MD, MPP copyright 2007Michael A.

Microsoft Access 2007 Introduction

Introduction to Querying & Reporting with SQL Server

Search help. More on Office.com: images templates

IN THIS PROJECT, YOU LEARN HOW TO

Computer Skills: Levels of Proficiency

Task Force on Technology / EXCEL

Physical Design. Meeting the needs of the users is the gold standard against which we measure our success in creating a database.

Administering a Microsoft SQL Server 2000 Database

Information Technology Grades Students will know and be able to: Basic Operations 1.1 (I)

Table and field properties Tables and fields also have properties that you can set to control their characteristics or behavior.

Microsoft Access 2010 Part 1: Introduction to Access

TIM 50 - Business Information Systems

How To Save Data On A Spreadsheet

Massachusetts Technology Literacy Standards

Microsoft Access 2010: Basics & Database Fundamentals

PBI365: Data Analytics and Reporting with Power BI

Access Queries (Office 2003)

Microsoft Office Topics per Course

Planning and Creating a Custom Database

Improving Productivity using IT - Level 3 Scenario Assignment Sample Test 4 Version SampleMQTB/1.0/IP3/v1.0. Part 1 Performance

Access 2010 Intermediate Skills

How to Define Authorizations

Microsoft Access 2010 Overview of Basics

Business Insight Report Authoring Getting Started Guide

Extension Course Notes, Attachments, and Document Management Version 9.0

ACCESS Importing and Exporting Data Files. Information Technology. MS Access 2007 Users Guide. IT Training & Development (818)

Excel 2007 Tutorials - Video File Attributes

Access Database Design

Administering a Microsoft SQL Server 2000 Database

Database Design and Normalization

Working with Spreadsheets

Intellect Platform - Tables and Templates Basic Document Management System - A101

MICROSOFT ACCESS TABLES

Transcription:

Today s discussion Practical Design In a research environment Kim Laursen, ITS Education Coordinator, 9-5674 Tom Reardon, ITS Senior Programmer/Analyst, 9-5671 What is a database? Steps in designing a relational database terminology and concepts Live Demo Common design problems Redesigning the database So, what exactly is a database? Manual/ Non-computerized Flat/ hierarchal Relational Rolodex Filing cabinet Telephone book Word labels Excel Worksheet Tree-like structure Access database SQL database Research data Patient information Student information Reasons for creating a computerized database Rapid access to information Eliminate or minimize duplication information Simplify data entry and reporting Accommodate expansion Maintain integrity of data Prevent access to unauthorized persons Provide statistics for analysis Provide summary data for papers, presentations Top Down Approach Bottom Up Approach Data model that is well organized Systems Planning Helps insure no data overlooked Designed Details can be easily overlooked Information Model Overall organization may not be so apparent Relationships Determined Proposed Data Entities Identified

Practical Design What is the purpose of your database? Combined Approach Cross check for both completeness and good organization Systems Planning Designed Write out statement of purpose How do you collect data? Information Model Relationships Determined Data Entities Identified Who enters it into the database, what is their experience level (with data and computers) What s the expected lifetime of the project? j t? Can the same form be used for multiple projects either now or in the future What kinds of analysis are you going to do? Proposed Who collects it Who will analyze the data Who will want reports Brainstorm questions about database Sketch out workflow - reports Gather current forms and reports Spreadsheet Strengths 1. Ease of data entry 2. Calculations and statistical functions available 3. Charting capabilities 4. Pivot table reports Spreadsheet Weaknesses 1. Hard to customize data entry for complicated situations 2. Not good at managing large amounts of data with complex relationships (patient records with multiple visits) 3. Hard to sort or select for specific subsets of data 4. Complex statistics are usually beyond its reach Good Excel Example Excel 1. Single table of data, fairly small amount 2. Numbers and financial data Avoid wrapped text in headings 3. Sophisticated what if models and cost benefit analyses 4. Charting and data bars 5. Pivot tables 6. Familiarity/preference UNMC ITS Helpdesk 559-7700 12/1/2010

Poor Example 13 Relational Management System Strengths 1. Manage and track large amounts of data 2. Powerful structure to develop queries to find specific information 3. Relatively easy to create data entry forms and reports in complex situations 4. Fairly easy to make relatively good, if not publication quality charts 5. Allows multiple user access at the same time 6. Relatively easy to import/export data from/to other applications Relational Management System Weaknesses 1. Limited statistical capability largely restricted to basic descriptive measures 2. Charting and graphing capability is often limited 3. Learning curve Access 1. Store and manage lots of data, especially repeated data 2. Keep track of actions or events? 3. More than one table related to each other 4. Want to create data entry forms 5. More complex filters/queries 6. Generate variety of reports 7. Multiple users entering data at the same time Access 2007 Making a relational database work Tables Forms Queries Reports Macros Modules

Rooms Tables where you store your data Furniture & Possessions Fields What you keep in the rooms records Common Design Problems Entrances, doors Forms & Reports - Ways of getting data into and out of the house Windows Queries -Ways of looking at what is in the house, from different perspectives Structural Design Flaws Additions, Deletions, and Updates behave unpredictably Inability to retrieve information efficiently Redundant information Inconsistent information Loss of information (zip codes) Doesn t export easily Preventable Data Entry Errors These are data entry errors that the system could either prevent, or provide a warning, if the right data validation rules are in place. 1. Data out of range 2. Using the wrong type of variable, entering mixed character and numeric data ie 98.6F 3. Loss of information due to rounding errors Operator Errors These are data entry errors that could not be caught by the system. Some examples would be: 1. Inconsistent spellings or terms for the same thing 2. Reversed letters and/or numbers 3. Wrong codes 4. Inaccurate entry within a variable s acceptable range How to avoid errors Three-pronged approach at table design and forms design level 1. Formal model constrains what can be done and insures data integrity 2. Data validation rules 3. Basic design principles, psychology

Steps in Designing a Purpose of your database Table(s) you ll need Fields in each table Relationships Refine your design Add data and create other database objects Tables Look at individual facts about the table Base table or lookup table Don t duplicate information Don t eliminate or delete valuable information Identify Facts about your TestID# Lab Tests Date RatID# TestIDCode Description Application RatID# Weight M/F DOB Rats Lab Test lookup Rat Fields Related to the subject of the table Don t include derived or calculated data Include all the information i that you need Store information in its smallest logical parts Avoid spaces in field names Primary key fields Primary Key Field Foreign field Primary key in one table, used to relate (join) records in another table. Has the same type and properties of the primary field (doesn t have to have the same name) Uniquely defines a row in a table Minimal size Stable should not change Simple and familiar

Other Keys Compound key Composed of two or more columns, such as DateDone and TestName (if a specific test is done only once per day) Surrogate key Doesn t come from the data, such as autonumber Determine Relationships One-to-one relationship inner join 31 One-to-many relationship outer join This is where a row in one table (the parent table) has one or more matching rows in a second (child) (hild) table. This is probably the most common relationship, Many-to-many relationship Row in table 1 has many matching rows in table 2, and a row in table 2 has many matching rows in table 1. Requires a third intermediate table Sample Relationship Screen Enter sample data Many empty fields? Refine your design Forget any fields? Duplicate information in your tables? Good primary key for each table?

More on Relationships and Referential Integrity Add data and other database objects Small number of records initially Continue to refine Create forms, queries, reports Test to see if you re getting the desired results Other considerations Updating and modifying data Indexes needed? d? Security Backup and recovery Documentation Tools > Analyze > Documenter Did you inherit someone else s database? terms Hierarchical database Relational database objects 1. Tables - tblname 2. Fields 3. Queries - qryname 4. Forms - frmname 5. Reports rptname 6. Properties Relationships 1. Primary keys 2. Foreign keys Referential integrity Validity Normalizing Sample Scenarios Birthday cards Home music library kl1 Home inventory Employee equipment inventory Research data on rat experiments

Slide 42 kl1 These are probably not appropriate for a research audience. Depending on time, we may not have time for this. I think more effective to show good and bad examples. klaursen, 10/19/2010

Building a Live Demo Tom Reardon 43 Where to Get More Information Detailed handout and recording of today s session at RUG web page www.unmc.edu/its/292.htm Training sessions- ITS Web page www.unmc.edu/its - classes and training link On-line resources http://office.microsoft.com DVD tutorials 6 th floor circulation desk of the Library Books, articles, electronic sources The Missing Manual for Access 2007 Matthew McDonald ITS Customer Support 559-7700 Academic programming Tom Reardon 9-5671 College courses