Sign In
Not register? Register Now!
Pages:
4 pages/β‰ˆ1100 words
Sources:
5 Sources
Style:
APA
Subject:
Health, Medicine, Nursing
Type:
Essay
Language:
English (U.S.)
Document:
MS Word
Date:
Total cost:
$ 17.28
Topic:

Database Schema for Storing Patient Information

Essay Instructions:

Design a database schema for the proposed project goals and objectives included in your proposal in Topic 1.
If you do not have access to ER modeling software or a diagramming tool like Visio or OmniGraffle, you can simply create diagrams in a presentation tool like PowerPoint. This is an essential skill that is used in the field.
This assignment will be utilized again in Topic 5. Prior to Topic 5, review any feedback provided to you by the instructor.
Part 1: Diagram
Identify and list all relevant entities and their relationships. Include the following:
Select no less than five entities.
Provide a diagram.
Map this to a database schema.
Provide a data dictionary for all entity attributes.

Part 2: Discussion
Include the following discussion with your diagram:
Identify one or two areas of your design that seemed especially difficult to develop. What difficulty did you encounter in modeling or mapping to the schema?
Based on project needs and the schema, discuss hosting considerations.
Discuss the required resources and estimated budget for the project.
In addition, provide the rationale for the design chosen, its limitations, and its possible extensions.
APA style is not required, but solid academic writing is expected.
This assignment uses a rubric. Please review the rubric prior to beginning the assignment to become familiar with the expectations for successful completion.
Hello the assignment related to order # 00083489 is related to deign, implementation and management of database systems and I have attached a sample provided by my instructor. Viewing the "Managing Databases" video might also help. I will go ahead and read these chapters and copy and paste what would be relevant to the topic. If you have any access to the readings that would also be helpful.
Read Chapters 3, 4, and 9 in Database Systems: Design, Implementation, and Management.
URL:
https://www(dot)gcumedia(dot)com/digital-resources/cengage/2018/database-systems_design-implementation-and-management_13e.php
Read Chapters 3, 4, and 9 in Database Systems: Design, Implementation, and Management.
URL:
https://www(dot)gcumedia(dot)com/digital-resources/cengage/2018/database-systems_design-implementation-and-management_13e.php
Read Chapter 16 in Database Systems: Design, Implementation, and Management.
URL:
https://www(dot)gcumedia(dot)com/digital-resources/cengage/2018/database-systems_design-implementation-and-management_13e.php

Essay Sample Content Preview:

Database Schema
Author Name
Institution Affiliation
While designing this database, I came across a number of problems: poor indexing and drawing a single table for all domain values. The Payment section was difficult to develop as I did not know how to index it properly and correctly. There are times when an application or user needs to query several columns of a table. As the number of rows was recorded, the table grew significantly and this impacted the time queries took to complete. To speed up the process and to reduce the effect of overall table size, I had to spend extra time in indexing the table columns, and this helped me make the entries visible instantly. For this purpose, I have to invoke a SELECT query, which sometimes leads to deterioration of the INSERT, UPDATE and DELETE commands. The indexes were to synchronize to the content of the database. The problem was finally solved by having a single index for all columns, and this was distinct from the main key I used to query the table.
Another significant problem was that an all-encompassing domain table did not prove to be as beneficial as I expected it to be for the database design. In the Bill section, it took me a lot of time and energy to mention the number of the bill, date of the bill and status of the bill. It should be noticed that a relational database is built around the idea that every object in the database will represent one thing only. As part of the normalization process, the breaking down and isolation of data ended in every row which represented a single thing.
While modeling or mapping the schema, I found it difficult to store or maintain data. When I used the code that could help access the database, it took me a lot of time to store and maintain the data (Elmasri, 2018). At this point, I felt that it was good to get a pro...
Updated on
Get the Whole Paper!
Not exactly what you need?
Do you need a custom essay? Order right now:

πŸ‘€ Other Visitors are Viewing These APA Essay Samples:

HIRE A WRITER FROM $11.95 / PAGE
ORDER WITH 15% DISCOUNT!