This week we focus on physical modeling design with the ‘representational aspects’ and the ‘operational aspects’ of the databas
This week we focus on physical modeling design with the "representational aspects" and the "operational aspects" of the database. In the following weeks, we work in the internal DBMS specific operations and processes and how the DBMS interacts with the data, the database and the user. The translation from logical design to physical design assigns "functions" to both the machine (the DBMS) and the user. Functions such as storage and security, and additional aspects such as consistency of data and learnability are dealt with in the physical model/schema. Practically speaking, a physical schema is the SQL code used to build the database.
You can use any of the Online SQL systems discussed in class, Microsoft Access, or download and install a SQL Script Editor for your computer. A copy of the SQL code is required for this assignment. You will build the front-end for the user (DBMS) at the end of the intersession weeks.
Use SQL statements to populate your Database Relational Schema data. Implement your design by generating a file of SQL to create the code script. This should include:the creation of tables, but also (as appropriate) the creation of named, data type, and constraints. Constraints are used to limit the type of data that can go in a table. This ensures the accuracy and reliability of the data in the table. If there is any violation between the constraint and the data action, the action is aborted.
NOTE:
create statements for the database, tables, views, procedures and such, all of which focus on the structure around the data. They are part of the Data Definition Language (DDL). You'll need to upload both the physical model ERD and the DDL SQL statements in your submission. The physical model is the logical model with the data types (int, char, varchar, date, timestamp, etc) included in the diagram (week3 diagram with data types). Let me know what platform the SQL statements are for that is, are you using SQL Server, MySQL, Oracle, Amazon's databases, Azure etc as they all have a common SQL base but have different nuances that I have to account for when I test the code. I challenge you to have both an introduction and a conclusion to your paper. attached are precious document
Running Head: DATABASE 1
DATABASE 3
Database
Student Name
Tutor’s Name
Date
Artist
Artist_ID
Name
Event
Event_ID
Date
Organizers
Organizer_ID
Name
Manager
Manager_ID
Name
Album
Album_ID
Title
Artist_ID
Year
Label_ID
Label
Label_ID
Name
Producer
Producer_ID
Name
Release
Release_ID
Date
1 1
*
*
1
1 *
*
1 1
* *
1
*
Reference
Schmidt & Brodie, M. L. (2018). Relational database systems: Analysis and comparison. Springer Science & Business Media.
Captain, F. A. (2018). Six-step relational database design: A step by step approach to relational database design and development. Fidel A Captain.
,
Running Head: Conceptual Modeling Design 1
Conceptual Modeling Design 4
Conceptual Modeling Design
Student’s Name:
Tutor’s name:
Date:
The entities to be used include the following:
· Artist.
· Manager
· Producer
· Event
· Album
· Organizers
· Label
· Release
Relationships
The manager manages all the activities that the artist should take part in including signing the artist, managing the artist’s resources, advising the artist etc. The producer deals with the music production part, together with the organizers, they organize events that the artist will perform at. The producer together with the manager oversea the recording and the release of albums.
Each of the entities will have various attributes as follows:
· Under the manager the primary key will be the manager’s ID, other attributes will include the manager’s name, address, and the phone number.
· Under the artist the PK will be the artist’s ID while the other attributes will be the name, address, genre of music, and the phone number.
· The producer’s section will include the name, address, phone number, the salary, and the producer’s ID.
· The event will have attributes such as the type of event, the amount to be charged per person, and the reference number of the event.
· The label will include the record label’s name, the amount they charge, the serial number of the record label.
· The release entity will attribute such as the release date, and the venue of the release.
ERD Blueprint.
The ERD shows the relationship between the various entities involved in the music production.
Organizers
Event
Producer
Artist
Album
Label
Release
Manager
Reference.
D’Angelo, A. (2016). Development of the reliability-risk modeling framework for ranking conceptual designs. Volume 14: Emerging Technologies; Materials: Genetics to Structures; Safety Engineering and Risk Analysis. https://doi.org/10.1115/imece2016-66791
Embley, D. W., & Thalheim, B. (2012). Handbook of conceptual modeling: Theory, practice, and research challenges. Springer Science & Business Media.
Mok, W. Y., & Embley, D. W. (1996). Transforming conceptual models to object-oriented database designs: Practicalities, properties, and peculiarities. Conceptual Modeling — ER '96, 309-324. https://doi.org/10.1007/bfb001993
Collepals.com Plagiarism Free Papers
Are you looking for custom essay writing service or even dissertation writing services? Just request for our write my paper service, and we'll match you with the best essay writer in your subject! With an exceptional team of professional academic experts in a wide range of subjects, we can guarantee you an unrivaled quality of custom-written papers.
Get ZERO PLAGIARISM, HUMAN WRITTEN ESSAYS
Why Hire Collepals.com writers to do your paper?
Quality- We are experienced and have access to ample research materials.
We write plagiarism Free Content
Confidential- We never share or sell your personal information to third parties.
Support-Chat with us today! We are always waiting to answer all your questions.
