Outcomes: Examine tables, columns, and datatypes for a database design. Create a

Responsive Centered Red Button

Need Help with this Question or something similar to this? We got you! Just fill out the order form (follow the link below), and your paper will be assigned to an expert to help you ASAP.

Outcomes:
Examine tables, columns, and datatypes for a database design.
Create a physical data model.
Synthesize database concepts needed to effectively design a database.
Purpose
The purpose of this assignment is to take the logical model and expand it into the physical model. All of the effort in previous steps to think through our design allows us to move forward with our physical implementation more easily and effectively. We can now refine our logical model into the physical data model which can then directly map between the diagram and the actual database management system.
Assignment Instructions
For this assignment, you will complete the physical model for your database design. This model will be based upon the logical model you created previously. Developing your physical model will require that you carefully document the definitions for your database that you will later implement in the database management system, Microsoft Access. Think carefully about the type of data you will be storing in each field.
Will it be numeric?
Will it be text?
Can it be left blank (null)?
You will use Microsoft Visio to build your physical ERD diagram which will include the following.
You may start with your existing logical diagram and modify it as follows:
As an additional challenge for this phase of the design, you will add one more table to the database design. Think of some other aspect of this business model that you could bring into the design at this point. You must plan out how this new table will relate to at least one other existing entity. Show the relationship using crows foot style of notation.
Table names. Include those from your conceptual diagram and the new table from the previous step. Remember to use meaningful names and consistent naming conventions.
Hint: these started out as entities
Field names. Identify appropriate field names for each table in your diagram. Remember to use consistent naming conventions. (i.e. clientID, petID, breedID might all be primary key fields).
Hint: these started out as your attributes
Reference: http://www.databasedev.co.uk/database_field_names.html
Primary keys/foreign keys. Notate the primary and foreign keys in each table as applicable. Remember to be consistent.
Hint: the primary key in the “one” table matches to the foreign key in the related table.
Data types and field sizes. Identify appropriate data types for each field and field sizes as applicable.
Hint: right-click your entity block and choose show attribute types to add a column to the right of your field names.
Nullability. Identify those fields that can be left blank.
Hint: You may simply identify those fields that may be left blank with a null indicator as shown in the example.
Assignment Requirements
You will build your diagram using Microsoft Visio. You may use the ERD template with crow’s foot notation as referenced previously. You will submit your Visio diagram file (*.vsd).

How to create Testimonial Carousel using Bootstrap5

Clients' Reviews about Our Services