Algorithm : 2023-24 and 2024-25 : Sample2

EX. No.1:

AIM:

The aim of this project is to optimize queries for an XML database that stores college
data, specifically focusing on retrieving student information efficiently.

ALGORITHMS:

 Create Table and to insert into the values

 Task 1: Write Basic Queries

Retrieve All Employee Details , Find Employees in a Specific Department , List

Employees Hired After a Specific Date, Retrieve Employees Sorted by Salary in
Descending Order

 Task 2: Access Metadata

Get the Structure of the Employees Table and View Existing Indexes on the Table

 Task 3: Analyze Query Performance

Analyze Performance of Queries Using EXPLAIN

For example, to analyze the performance of the query to retrieve all employee details:
 Task 4: Optimize Queries

1. Create an Index on the Department Column

2. Rewrite Queries to Utilize Indexes More Effectively
For example, if you frequently query employees by department, ensure the query uses
the index:

 Task 5: Evaluate Optimized Queries

1. Re-run the EXPLAIN Command on Optimized Queries

For the optimized query:

=============== ==============================

Ex.No.2:
AIM: Create and manage tables in two distributed databases, insert data, combine data using
SQL operations, handle duplicates, and aggregate information.

ALGORITHMS:

Table Creation:

 Define table schemas for Employees, Departments, and Salaries.

 Create these tables in both Database1 and Database2.

Data Insertion:

 Insert sample data into each table in both databases.

Data Combination Using UNION:

 Write a SQL query to combine data from Employees tables in both databases using
UNION.

Handling Duplicates with UNION ALL:

 Modify the previous query to use UNION ALL to include duplicates.

View Creation for Aggregation:

 Create a view that aggregates employee data, such as total and average salaries by
department.

Query the View:

 Write a SQL query to retrieve aggregated data from the view.

=================== = ==================================

Ex.No.3:

AIM: To write OQL queries that retrieve various data from an object-oriented database
containing information about employees, departments, and projects.

ALGORITHMS:
1. Retrieve All Details of Employees : Select all attributes from the Employee class.

2. List Employees in a Specific Department ("Engineering"): Filter employees by

departmentName in the Department class.

3. Find Employees with Salary Above $70,000: Filter employees by salary.

4. Find Employees Managed by a Specific Manager (employeeID = 1002): Join Employee

with Department and filter by manager ID.

5. Find Employees Involved in a Project Named "Project X": Join Employee with Project
and filter by project name.

6. Count the Number of Employees in Each Department: Group by department name and
count employees.

7. Retrieve Employees Hired After January 1, 2021: Filter employees by hire date.

8. List Projects and Their Respective Team Members: Join Project with Employee to get
team members.

9. Find Employees Not Assigned to Any Project: Filter employees with no associated
projects.

10. List Departments with Their Managers: Fetch department details and join with
manager information.

================= ========================================

Ex.No 4:

AIM:

 To set up and configure Apache HBase as a parallel database system.

 To perform basic CRUD operations using Python.
 To leverage parallelism in data operations.
 To optimize database queries for performance

ALGORITHM:

 Setup and Configuration: Install Apache HBase and configure it with Python
environment.
 Connection Establishment: Write Python code to connect to HBase.
 CRUD Operations: Implement Python code to perform INSERT, SELECT,
UPDATE, and DELETE operations.
 Parallel Operations: Use concurrency utilities to perform batch operations and
measure performance.
 Query Optimization: Apply optimization techniques to enhance query performance
==================== ==========================================

Ex.No.5:

AIM:

To create an active database that stores facts about a company's domain (e.g., employees,
departments, and projects) and to define rules that derive new facts or retrieve specific
information based on stored data.

ALGORITHMS:

Design the Schema:

 Define the schema for the active database, including tables for employees,
departments, and projects.
 Identify key attributes and relationships among the tables.

Define and Store Facts:

 Populate the database with initial facts about employees, departments, and projects.
 Implement mechanisms to dynamically insert and delete facts.

Define Rules:

 Create rules to derive new facts or perform specific operations when certain
conditions are met.
 Ensure that rules are automatically triggered when related facts are inserted, updated,
or deleted.

Test Rules and Complex Rules:

 Validate the behavior of simple rules.

 Design and test complex rules that involve multiple conditions and actions.

Dynamic Fact Management:

 Insert and delete facts dynamically.

 Ensure that rule evaluations are performed correctly based on the changes.

================== =========================================

Ex.No.6:

AIM:
To create a deductive database that stores and retrieves information about humans, their
characteristics, and their relationships, and to support inference to derive new facts from
predefined rules.

ALGORITHMS:

Algorithms

1. Database Schema Creation:

o Define predicates to represent the database schema.
o Create rules for inferencing based on the stored data.
2. Data Insertion:
o Insert sample data into the database.
3. Query Execution:
o Define queries to retrieve specific information.
o Implement recursive rules for complex inferencing.

=================== ===============================

Ex.No.7:

AIM: Enhance the ETL (Extract, Transform, Load) process to not only load data from
multiple sources but also perform aggregations and enrich the dataset with additional
information.

ALGORITHMS:

Source Data Preparation:

 Source 1: CSV file with production data.

 Source 2: SQL database with sales data.

Design Target Schema:

 Target Table 1: Production

o Fields: ProductID, ProductName, ProductCategory
 Target Table 2: Sales
o Fields: SaleID, ProductID, SaleDate, QuantitySold, SaleAmount
 Target Table 3: MonthlySalesSummary
o Fields: ProductID, Month, TotalQuantitySold, TotalSaleAmount

ETL Tool Setup:

 Extract:
o Import data from the CSV file and SQL database.
 Transform:
o Aggregation:
  Aggregate sales data from the SQL database by month and product to
calculate TotalQuantitySold and TotalSaleAmount.
o Enrichment:
 Enrich the production data by adding a ProductCategory based on
predefined rules or external data.
 Load:
o Insert the transformed and aggregated data into the Production, Sales, and
MonthlySalesSummary tables.

Validation:

 Verify that the data in the MonthlySalesSummary table is correct by checking

aggregation results and comparing them against raw sales data.

=============== =============================================

Ex.No.8:

AIM:

To demonstrate how to efficiently manage and retrieve a large dataset of employee

information stored in separate tables for different departments using Oracle DB.

ALGORITHM:

Create Tables:

 Create two tables, employee_department1 and employee_department2, to store

employee data separately for different departments.

Insert Data:

 Insert a large amount of sample employee data into these tables to simulate a real-
world scenario with voluminous data.

Display Sample Data:

 Retrieve and display a subset of the data from both tables to verify that the data has
been correctly inserted.

Combine Data:

 Use the SQL UNION operation to combine the data from both tables. This operation
eliminates duplicate records and provides a unified view of all employee data.

Retrieve and Display Combined Data:

  Retrieve and display the combined data, applying filters to demonstrate data retrieval
based on specific criteria such as age or salary.

Output for Specific Criteria:

 Retrieve and display data for employees aged between 30 and 40.
 Retrieve and display data for employees with a salary greater than 60,000.

=============== ==========================

ExNo. 9:

AIM:

To leverage MongoDB to efficiently manage and analyze data related to inventory, employee
information, and production tracking.

ALGORITHM:

Database Design:

 Collections: Define collections for Inventory, Employees, and Production.

 Documents: Structure documents in each collection to capture relevant data.

CRUD Operations:

 Create: Insert new records into each collection.

 Read: Retrieve and query records from the collections.
 Update: Modify existing records.
 Delete: Remove records from the collections.

Aggregation Pipelines:

 Use aggregation to analyze and summarize data (e.g., total inventory value, employee
performance metrics).

Indexing and Schema Design:

 Implement indexes to optimize query performance.

Design schemas to handle evolving data requirements efficiently

================= =================================

Ex.No.10:

AIM:
This web application is to enable a company to manage employee information effectively.
The application will allow administrative staff to perform CRUD (Create, Read, Update,
Delete) operations on employee records, ensuring a smooth and efficient way to handle
employee data.

ALGORITHM:

Setup Environment

 Install a local server environment like XAMPP or WAMP that includes PHP and
MySQL.
 Create a MySQL database and table for storing employee information.

Connect PHP to MySQL

 Establish a connection to the MySQL database using PHP’s mysqli or PDO extension.
 Create functions for CRUD operations.

Build User Interface

 Design HTML forms for adding, viewing, updating, and deleting employee records.
 Use PHP to handle form submissions and display data.

Implement Form Validation and Sanitization

 Validate user input to ensure it meets expected formats and constraints.

 Sanitize input to prevent security vulnerabilities.

Basic Security Measures

 Implement prepared statements to prevent SQL injection.

 Use secure password hashing for user authentication if required.

=================== ======================================