Using the relations that you defined and normalized as part of the unit 4 assignment posted above, create the SQL DML statements necessary to implement your database schema as an OpenOffice database. You may also implement your database in MySQL, IBM DB2 Express, or Microsoft Access if you have access to these database systems. Your assignment must include a document that contains all of the SQL statements that you created and a screen shot that shows the structures that you implemented in the database of your choice. Your DML statements must accommodate the following elements:

Create statements to create tables from the entities defined as part of the Unit 4 assignment

Appropriate use of Null (and Not Null) parameters to ensure data validity

Appropriate use of constraint clauses to implement appropriate referential integrity

Use of data types and formats that is appropriate for the data in your database schema.

Appropriate use of keys including automatic generation of key values if appropriate

Assignment Instructions:

the assignment must include the SQL DML statements required to implement at least the following relations:

Book

Borrower

BookLended

Librarian

the assignment must make appropriate use of Null (and Not Null) parameters to ensure data validity. The minimum standard will be measured against the instructors example and will be based upon rules associated with primary and foreign keys and integrity constraint rules.

the assignment must make appropriate use of constraint clauses to ensure the referential integrity of the relations in the schema. The minimum standard will be measured against the instructors example and will be based upon rules associated with primary and foreign keys and integrity constraint rules. NOTE: the unary relationship that we defined for the librarian relation is NOT required as part of this assignment.

the assignment must make appropriate use of keys including the automatic generation of key values where appropriate.

VEW Avery AaBbCcl AaB AaBI AaBb AaBbCcl AaBb Aat AaBbCcl AaBbCcl Caption Heading1 Heading 2 Heading 3Normalle itle No Spac. Subtle Em. Styles Borrowe IS8N Tit Author Publication date date Character Character Character PhoneNumber Character Name addres racter Character PostalcodeC number Membershipdate Date Booktended Librarycard integer librarianID integer I SEN-Number integer Checkoutbate date Librarian Name Character PhoneNumber Integer Here is the initial library database. So what are relations that should undego normalization? For the Book Relation 1st Normal Form. I think we can find many book which can be written by the same author. So even ifI think the attribute Author can be essential but it can be removed from the relation. I think there is no problem with the Borower relation because I think each borrower is unique we can't find two borrowers having the same name and everything revolve around the attribute