1. SQL, Data Storage Technologies, and Web-Data Integration Week 2

2. Today’s Agenda Review First Week Data Modeling, ER Diagrams Normalization techniques –2 nd Normal Form –3 rd Normal Form Physical Data Model

3. First Normal Form First Normal Form (1NF) occurs when all attributes are single valued. –No repeating or attributes with multiple values Examples: –A Movie entity with attributes actor1, actor2, actor3. –A Sundae entity with a “toppings” attributes

4. In Class Exercise Create an Data Model in 1 st Normal Form for the following applications: 1.Recipes 2.Dating Service 3.Bookstore 4.Photo Sharing 5.Movie Collection

5. 1 st NF Data Model / ER Diagram

6. ER Diagram Terminology NULL: The database term for a value that does not exist. –What attributes in our data model could be NULL? Unique Identifiers (IDs) –Every entity needs a Unique Identifier –It must be unique across all instances of an entity –It must not be NULL –Its value must never change.

7. Unique Identifiers How do we pick IDs? –From attributes What are the IDs in our data model? –Auto-generated IDs Very common Security Issues

8. Relationships An association between two entities Indicates the degree of the relationship –one and only one (also zero or one) –one or many (also zero or many) Examples: –A Donor gives one or many Donations –A Donation is given by one and only one Donor What are the relationships in our model?

9. Relationships Three degrees make three types of relationships One to one –rare One to many –very common Many to many –will need special handling

10. ER Diagrams Entities are rectangles Attributes are ellipses Unique IDs are underlined Relationships are lines between entities –Straight line for one and only one –“Crow’s foot” for one or many –Can use bars and circles to represent one or zero

11. Data Model Relationships

12. Junction Entities Many to many relationships can be hard to represent in a RDBMS They are replaced with junction entities –Take the many-to-many relationship –Replace it with an entity –Create two new one-to-many relationships to the new entity Which side should the “many” be?

13. Data Model with Junction Entity

14. New Example Data Donor IDNameAddressPhoneEmail 1Fred Smith 123 Bedrock 555- 1212 f@fred. com 2Beth Kirsh 104 Ballard 555- 1234 b@kirsh.com 3Erin Lovett 1580 Stone Ln 555- 5098 e@erin. com Donation IDAmountDateP Name 1100.0001/02/04Martha 2250.0012/11/04Jim 310.0009/07/04Jim 4100.0002/02/04Jim Division IDName 1Marketing 2Child-care 3Trips DonationToDivision IDPercentage 1100% 250% 3

15. ER Diagram Terminology Non-identifying attribute: An attribute that is not the Unique ID and is dependent on the Unique ID. Repeating entries are often a sign of an non-dependent attribute Examples: –Is Donor Name a non-identifying attribute? –Is Processor name?

16. 2 nd Normal Form (2NF) Model has to be in 1NF All attributes must be non-identifying attributes. To make 2NF, we have two options –Create a new entity for the attribute –Move the attribute to the entity where it really belongs

17. 2 nd Normal Form

18. Don’t simply look for repeating entries to determine 2NF Example: Is percentage already in 2NF? Many entries have 100% for their value –Yes –The value is dependent on the DonationToDivisionID –Percentage also doesn’t make sense as an Entity: it has no attributes other than itself, and 75% isn’t a “thing”.

19. 3 rd Normal Form Must already be in 2 nd normal form Non-identifying attributes cannot be dependent on each other. Examples: –Employee(eid, name, position, salary) –Address(street, city, state, state abbr.) Move the dependent attributes into a new Entity

20. 3 rd Normal Form

21. In Class Exercise Update your Data Models to 3 rd Normal Form for the following applications: 1.Recipes 2.Dating Service 3.Bookstore 4.Photo Sharing 5.Movie Collection

22. Physical Database Design ER Diagram completed – review design carefully Time to convert our conceptual ER diagram into a real database system.

23. Physical Database Design Step 1 –Convert all entities into tables A database is typically made up of many tables A table is made up of columns and rows Each row in a table represents one instance of the entity

24. Physical Database Design Step 2 –Attributes become columns in the tables Important to pick the appropriate data type for the columns More on data types later

25. Physical Database Design Step 3 –Unique IDs become primary keys Remember, they cannot be NULL, and no duplicates are allowed Primary key is the just the database name for an entity’s unique ID – Primary keys are automatically indexed by the database (more on this later)

26. Physical Database Design Step 4 –Relationships become foreign keys in one table of the relationship. A foreign key is a unique ID of another table. –This creates a reference to a unique row in another table This simply means we have a column in one table that contains the unique ID of the other table.

27. Physical Database Design Step 4 Continued Which table does the foreign key belong in for a one-to-many relationship? –Store the unique ID from the "one" side of the relationship in the table representing the "many" side of the relationship

28. Physical Database Design Donor DonorIDNameEmailaddressPhone number Donation DonationIDDateAmountDonorIDProcessorID Processor ProcessorIDname DonationToDivision DonationToDivisionIDPercentageDonationIDDivisionID Division DivisionIDname

29. Primary Keys & Unique IDs http://www.extension.washington. edu/dl/webulearningobjects/media _fit/ids.html

30. Data Types Each database has its own data types –Most share a common core of data types, including integers, character strings, and dates. MySQL has 36 different data types

31. Data Types Numeric Types –store numeric data such as integers and floating point numbers –Modifiers: UNSIGNED: 0 to 255 instead of -128 to 127 AUTO_INCREMENT: integers only, one per table

32. Data Types Numeric Types Cont.

33. Data Types String Types –store textual data. –Modifiers: BINARY: allows case-sensitive searching

34. Data Types String Types Cont.

35. Data Types Date types –store dates and times

36. Data Types Complex data types –Enumerations (ENUM) list of predefined strings, value must be one of them. –Sets (SET) list of predefined strings, value can be any combination of them.

37. Current Physical Database Design Donor DonorIDNameEmailaddressPhone number Donation DonationIDDateAmountDonorIDProcessorID Processor ProcessorIDname DonationToDivision DonationToDivisionIDPercentageDonationIDDivisionID Division DivisionIDname

38. New Physical Database Design Donor table: includes types!

39. Physical Database Design Choosing Column Options –Column options help enforce data integrity –Can make the programmer’s job easier –Which makes the DBA’s job easier Column Options –NULLs allowed, default values, auto incrementing values, and keys

40. Column Options NOT NULL –By default, columns can contain a NULL instead of a value; this overrides that behavior –Requires that some value always exists in that column for any given row of data. –Will cause a database error if the programmer tries to add a NULL to that column. –What should be NOT NULL in our donation ER diagram?

42. Column Options DEFAULT value –If a user doesn’t supply a value for a column, you can specify a default value –Example: For a local organization, State and Country might default to WA, USA –Should there be any DEFAULT columns in our donation database?

43. Column Options AUTO_INCREMENT –Provides a default value to an INTEGER column –The value will automatically be incremented for each insert –Only one column per table can have this option. –Great option for an internal (meaning not shown to a external user) primary key

44. Column Options PRIMARY KEY –Creates an index on the column –Forces each column entry to be unique from all other column entries –Automatically is NOT NULL UNIQUE –Just like PRIMARY KEY, without the special name.

45. Physical Database Design Now includes column options!

46. Relational Database Schema We now have our database schema Whereas our E/R Diagram was very abstract, we now have a very concrete, relational design Requirements / Ideas Database Schema E/R DiagramRDBMS

47. In Class Exercise Turn your Data Models into Database Schemas: 1.Recipes 2.Dating Service 3.Bookstore 4.Photo Sharing 5.Movie Collection