Professional Documents
Culture Documents
Data Management
By Tejas G S
ASSIGNMENT
Module Code: 19BNA502B
Programme: MBA
Batch: 2021
Reg. No 21MCMS101200
Declaration
The assignment submitted herewith is a result of my own investigations and that I have conformed to
the guidelines against plagiarism as laid out in the Student Handbook. All sections of the text and
results, which have been obtained from other sources, are fully referenced. I understand that cheating
and plagiarism constitute a breach of University regulations and will be dealt with accordingly.
Signature of the Module Leader and date Signature of Reviewer and date
3
Faculty of Management and Commerce
Ramaiah University of Applied Sciences
Department Management Studies Programme MBA in Business Analytics
Semester III Batch 2021
Course Code 19BNA502B Course Title Data Management
Course Leader Shilpa R.G.
Continuous Evaluation
Marks
Max Marks
Evaluator
Sections
Marking Scheme
Second
Marks
RBL
CO
PO
Designing suitable Database Schema for any Service Sector
A.1 for collecting large datasets efficiently from varied sources 05 3, 4 2,4 2,3
including ERP.
Creating associated tables by using Create Table Construct
A.2 05 3, 4 2,4 3
Assignment
by SQL Commands
A.3 Updating all tables by inserting 2 values in each table 05 3, 4 2,4 3
Developing relationship between tables and normalizing
A.4 the data using 2NF/3NF. Defining Primary Key, Foreign, Key 05 3, 4 2,4 3
and
Composite Keys for the same
A.5 Individual Presentation and Class Participation 05 3, 4 2,4 3
Assignment – Maximum Marks 25
4
A.1) Designing suitable Database Schema for any Service Sector for collecting large
datasets efficiently from varied sources including ERP.
The ERP system connects every operator and user to every other user on the plant floor as well as to
every other plant floor in the company. The most effective supply chain is one that is operations-
centric, where information is shared between and within factories and where real-time planning is
possible. ERP offers the necessary assistance to corporate processes in a consistent and efficient
manner. Additionally, the technology makes it possible to control information in a production
environment using real-time factory floor data.
We can complete the task with the help of an ERP designed for the cosmetics and personal care
sector. Employees will be able to fine-tune all parameters and consistently manufacture the goods
that your consumers depend on by keeping and updating your ingredient quantities, specifying
manufacturing methods, and applying them all via a completely configurable digital backend.
Designing a suitable database schema for collecting large datasets efficiently from varied sources
including ERP requires careful consideration of the data types, relationships, and data volume. Here
is a high-level outline of the steps involved in designing such a database schema:
Identify the data sources: Determine the sources of data to be collected. These may include
internal systems such as ERP, CRM, HRMS, etc., as well as external sources such as social
media, web analytics, customer feedback, etc.
Define the data entities: Identify the different types of data that need to be collected and
stored, such as customer data, sales data, financial data, product data, etc. Create a list of
these entities and their attributes.
Determine the relationships: Identify the relationships between the data entities. For
example, customers may purchase products, products may belong to categories, and
categories may have subcategories. Determine the cardinality of each relationship (one-to-
one, one-to-many, many-to-many) and the type of relationship (strong, weak).
Determine the data volume: Estimate the size of the data that will be collected and stored.
This will help determine the appropriate database technology and infrastructure required to
handle the volume of data.
Choose the appropriate database technology: Choose a database technology that can
handle the volume of data and support the required features and functionalities. For
example, a relational database management system (RDBMS) may be suitable for a service
sector that requires transactional data management, whereas a NoSQL database may be
more suitable for unstructured data such as social media feeds.
5
Create the database schema: Use the information gathered in steps 1-5 to create the
database schema. Define the tables, columns, and relationships, and establish the
appropriate data constraints and integrity checks. Optimize the schema for performance and
scalability.
Implement the database schema: Create the database, tables, and indexes according to the
schema design. Populate the tables with the initial data from the varied sources.
Develop the data collection and integration process: Develop a process for collecting and
integrating data from the various sources into the database. This may involve creating data
connectors or ETL (Extract, Transform, Load) pipelines to extract, transform, and load data
from various sources into the database.
Test and optimize the database schema: Test the database schema and data collection
process to ensure that they are working as expected. Optimize the schema and the data
collection process as needed to improve performance and efficiency.
Monitor and maintain the database: Monitor the database to ensure that it is functioning
correctly and efficiently. Perform regular maintenance tasks such as backups, updates, and
performance tuning to keep the database running smoothly.
By following these steps, you can design a suitable database schema for collecting large datasets
efficiently from varied sources including ERP in a service sector.
Table: patients
Columns:
Table: diagnoses
Columns:
6
diagnosis_id (INT, primary key)
diagnosis_name (VARCHAR)
description (VARCHAR)
Table: patient_diagnoses
Columns:
patient_diagnosis_id (INT, primary key)
patient_id (INT, foreign key references patients(patient_id))
diagnosis_id (INT, foreign key references diagnoses(diagnosis_id))
diagnosis_date (DATE)
doctor_name (VARCHAR)
7
A2. Creating associated tables by using Create Table Construct by SQL Commands.
1. PATIENT:
2. DIAGNOSIS :
3. TEST :
DIAGNOSIS Table
TEST Table
9
A4. Developing relationship between tables and normalizing the data using
2NF/3NF. Defining Primary Key, Foreign, Key and Composite Keys for the same.
10
Reference:
11
12