ASSIGNMENT

Module IV: Databases and Data Warehouses

1. Find at least five e-Business websites that are connected to database
management systems.
(Hint: look for something that indicates it is retrieving business data.?

Answer:
Here are five e-business websites that are connected to database management systems and
retrieve business data:
1. Amazon (www.amazon.com): Amazon is one of the largest e-commerce platforms that
heavily relies on a sophisticated database management system. It retrieves and stores vast
amounts of product information, user data, and transactional details.

2. eBay (www.ebay.com): eBay is another popular online marketplace that utilizes a database
management system to handle product listings, bidding data, customer information, and order
tracking. This retrieval of business data is crucial for efficient online transactions.

3. Uber (www.uber.com): Uber, the ride-hailing service, relies on a database management

system to ensure seamless coordination between drivers and passengers. It retrieves real-time
data on drivers' availability, geographic locations, and customer details for effective ride
matching.

4. Airbnb (www.airbnb.com): Airbnb, a leading hospitality marketplace, heavily relies on a

database management system to connect hosts with travelers. It retrieves business data
related to listing availability, pricing, host profiles, and guest information to facilitate
bookings.

5. Zillow (www.zillow.com): Zillow, a prominent real estate platform, uses a database

management system for retrieving property information, including listings, sales history,
price trends, and neighborhood data. This information empowers users to make informed
buying or renting decisions.
These websites demonstrate how database management systems play a critical role in
retrieving and managing business data, enabling efficient e-commerce operations.
2. List some of the problems of the traditional file environment.?

Traditional file environments, while once widely used, have several limitations and
problems, including:
1. Data Redundancy: Data is often duplicated in multiple files, leading to redundancy. This
wastes storage space and can result in inconsistencies if not properly maintained.
2. Data Inconsistency: Updates or changes to data in one file may not be reflected in other
related files, leading to inconsistencies and potential errors.
3. Data Isolation: Data in traditional file systems is often isolated and separated by
departments or applications, making it challenging to access and share data across the
organization.
4. Data Dependence: Application programs are closely tied to the structure and format of the
data files, making it difficult to make changes to the data without affecting the programs.
5. Lack of Security: Traditional file systems often lack robust security features, making it
easier for unauthorized users to access or modify data.
6. Limited Data Integrity: Ensuring data integrity (accuracy and consistency) can be
challenging in traditional file systems, as there are no built-in mechanisms for enforcing data
integrity rules.
7. Limited Concurrent Access: Concurrent access by multiple users can lead to problems like
data corruption or overwriting each other's changes, as traditional file systems often lack
mechanisms for managing concurrent access.
8. Scalability Issues: As an organization grows, managing and maintaining a large number of
files becomes increasingly complex and inefficient.
9. Backup and Recovery Challenges: Traditional file systems may not offer efficient backup
and recovery mechanisms, making it difficult to recover lost or corrupted data.
10. Difficulty in Querying Data: Extracting meaningful information from a traditional file
environment can be challenging, as it often requires writing custom programs to query and
analyze data.
11. Lack of Data Relationships: Traditional file systems typically do not support the
establishment of relationships between different sets of data, making it hard to represent
complex data structures.
12. Limited Data Sharing: Sharing data between different applications or departments can be
cumbersome and may require custom integration efforts.
To address these issues, many organizations have transitioned to modern database
management systems (DBMS) that offer better data organization, security, and management
capabilities.
3. Assume that you need to buy a DBMS for a midsize company. Research the
components needed and the approximate cost of at least two database
management systems.?

Certainly, when selecting a database management system (DBMS) for a midsize company,
you should consider various components and factors including the type of DBMS, licensing
costs, hardware requirements, and ongoing maintenance costs. Here, I'll provide information
on two popular DBMS options and their approximate costs:
1. Microsoft SQL Server:
Components Needed:
 SQL Server Database Engine (Core component)
 SQL Server Management Studio (SSMS) for administration
Additional components for specific features (e.g., Reporting Services, Analysis Services,
Integration Services)
Approximate Costs:
Licensing costs vary depending on the edition (e.g., Standard, Enterprise) and the
number of cores required.
As of my last update in September 2021, SQL Server Standard Edition costs around
$3,717 per core. Enterprise Edition costs considerably more.
SQL Server Management Studio (SSMS) is a free tool for managing SQL Server
databases.
Hardware Requirements:
Hardware costs depend on the server specifications needed to meet your performance and
capacity requirements.
Ongoing Costs:
Ongoing costs include licensing for additional features, maintenance, and support.
2. MySQL:
Components Needed:
MySQL Database Server
MySQL Workbench for administration and development

Approximate Costs:
MySQL is available in several editions, including the Community Edition (open source)
and the Enterprise Edition (commercial).
The Community Edition is free to use but may lack some advanced features.
MySQL Enterprise Edition costs depend on factors like the number of server instances
and support levels required.
Hardware Requirements:
Hardware costs will depend on the server specifications needed for your workload.
Ongoing Costs:
Ongoing costs may include support and maintenance fees if you opt for the MySQL
Enterprise Edition.
These costs are approximate and can vary based on factors such as the number of users, the
 scale of your database, and any specific needs of your company. Additionally, licensing
models and pricing structures may have changed since my last update in September 2021, so
it's essential to consult the respective vendors' websites or contact their sales teams for the
most current pricing information and to discuss your specific requirements.

4, Describe the concept of data modeling in detail with suitable example?

Answer:

Data modeling is the process of creating a structured representation of data, typically in

the form of a diagram or a set of rules, to facilitate the efficient storage, retrieval, and
manipulation of data in a database. It serves as a blueprint for designing and organizing
data in a way that meets the specific needs of an organization or application. Here's a
detailed explanation with a suitable example:
Key Concepts in Data Modeling:
1. Entities: These are the real-world objects or concepts that we want to represent in the
database. Each entity is typically represented as a table in a relational database. For
example, in a library database, "Book" and "Author" could be entities.
2. Attributes: Attributes are properties or characteristics of entities. They are the columns
in a table. For the "Book" entity, attributes could include "Title," "ISBN," "Publication
Year," and "Genre."
3. Relationships: Relationships describe how entities are related to each other. They define
how data in one entity is linked to data in another. For example, the relationship between
"Book" and "Author" indicates that an author can write many books, while a book is
written by one or more authors.
4. Keys: Keys are used to uniquely identify records within a table. Primary keys are
unique identifiers for each record in a table, while foreign keys establish relationships
between tables.

Example of Data Modeling:

Let's take a simplified example of a data model for a library management system:
Entities:
1. Book: Attributes could include ISBN (Primary Key), Title, Publication Year, Genre,
and Copies Available.
2. Author: Attributes could include Author ID (Primary Key), Name, and Biography.
Relationships:
A "Book" is written by one or more "Authors," and an "Author" can write many "Books."
This is a many-to-many relationship, so we need a junction table.
Book_Author: This table establishes the relationship between "Books" and "Authors." It
might have attributes like Book_ID (Foreign Key) and Author_ID (Foreign Key).
With this data model, you can efficiently organize and retrieve information about books
and authors. For example, you can easily find all books by a specific author or determine
how many copies of a particular book are available in the library.
Data modeling is a crucial step in database design as it helps ensure that data is organized
logically and efficiently, reduces redundancy, enforces data integrity, and provides a
foundation for building database systems that meet business or application requirements. It
also plays a significant role in ensuring that the database can adapt to future changes and
expansions.

5. Describe data retrieval.

Answer:

Data retrieval is the process of fetching or extracting specific information or records from a
database or data storage system. It involves searching, selecting, and presenting data that
matches specific criteria or requirements. Here's a breakdown of data retrieval:
1. Query Formation: Data retrieval begins with the formulation of a query. A query is a
request for data, typically written using a structured query language (SQL) for relational
databases. The query specifies the criteria that the retrieved data must meet. For example,
you might write a query to retrieve all books published after a certain year or all customers
from a specific region.
2. Query Execution: Once the query is written, it is submitted to the database management
system (DBMS). The DBMS processes the query, which involves parsing it, optimizing it for
efficient retrieval, and executing it against the database.
3. Search and Filter: During query execution, the DBMS searches the database's data tables
or other data structures to identify records that match the specified criteria. It applies filters
and conditions as outlined in the query to narrow down the selection.
4. Data Retrieval: The DBMS retrieves the selected data, which may consist of one or more
records or rows from one or more database tables. This data is typically stored in a temporary
result set.
5. Data Presentation: After retrieving the data, it is presented in a format suitable for the user
or application. This could involve formatting it into a table, JSON, XML, or another
structured format. The presentation might also involve sorting, grouping, or aggregating data
as required.
6. Output or Display: The retrieved and formatted data is then presented to the user through
an application interface, report, or directly in the user interface of a software application. The
user can view, analyze, or further manipulate the data as needed.
7. Error Handling: Data retrieval processes may encounter errors or exceptions, such as
connection issues, invalid queries, or data inconsistencies. Proper error handling is essential
to ensure that users receive informative error messages and that the system can recover
gracefully from errors.
8. Performance Optimization: Efficient data retrieval is crucial for database performance.
Techniques such as indexing, caching, and query optimization are used to speed up the
retrieval process, especially in large and complex databases.
Data retrieval is a fundamental operation in database systems, as it enables users and
applications to access and utilize the stored information. The effectiveness of data retrieval
depends on the design of the database schema, the efficiency of query execution, and the user
interface through which data is presented.