Thanks to visit codestin.com
Credit goes to www.scribd.com

0% found this document useful (0 votes)
28 views6 pages

Adbms Lab Manual

The document is a lab manual for Advanced Database Management System (ADBMS) practicals, outlining various implementations such as Object-Oriented Databases, Parallel Databases, and Deadlock Detection Algorithms. Each section includes objectives, prerequisites, steps, and expected outcomes for tasks like creating triggers, building knowledge databases, and designing XML schemas. The manual serves as a comprehensive guide for students to gain hands-on experience with advanced database concepts and tools.

Uploaded by

Mahesh Dahiwal
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
28 views6 pages

Adbms Lab Manual

The document is a lab manual for Advanced Database Management System (ADBMS) practicals, outlining various implementations such as Object-Oriented Databases, Parallel Databases, and Deadlock Detection Algorithms. Each section includes objectives, prerequisites, steps, and expected outcomes for tasks like creating triggers, building knowledge databases, and designing XML schemas. The manual serves as a comprehensive guide for students to gain hands-on experience with advanced database concepts and tools.

Uploaded by

Mahesh Dahiwal
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 6

Lab Manual for Advanced Database Management System

(ADBMS) Practicals

1. Implementation of Object-Oriented Database – Extended En-


tity Relationship (EER)
Duration: 1 Hour
Objective:
• To design and implement an Object-Oriented Database using Extended Entity Relationship (EER)
concepts.
• To understand inheritance, generalization, specialization, and aggregation in EER.
Prerequisites:
• Knowledge of ER diagrams and Object-Oriented Programming (OOP) concepts.
• Tools: Oracle Database with Object-Relational features.
Steps:
1. Identify the entities, attributes, and relationships for a given problem statement (e.g., a university
database).
2. Extend the ER diagram to include inheritance, generalization, and aggregation.
3. Use Oracle’s Object-Relational features to create object types and tables.
4. Implement relationships using REFs and nested tables.
5. Test the database by inserting sample data and querying it using Oracle SQL.
Expected Outcome:
• A working Object-Oriented Database with EER concepts implemented in Oracle.
• Queries demonstrating inheritance and relationships.

2. Implementation of Parallel Database


Duration: 3 Hours
Objective:
• To understand the architecture of parallel databases.
• To implement a parallel database system for improved performance.
Prerequisites:
• Knowledge of database partitioning and parallel processing.
• Tools: Oracle Real Application Clusters (RAC).
Steps:

1
1. Set up Oracle RAC for a distributed environment.
2. Partition a large dataset across multiple nodes.
3. Execute queries in parallel and observe performance improvements.
4. Compare the performance of parallel queries with single-node queries.
Expected Outcome:
• A functional parallel database system using Oracle RAC.
• Performance analysis report comparing parallel and single-node execution.

3. Implementation of Parallel Join and Parallel Sort


Duration: 3 Hours
Objective:
• To implement parallel join and sort algorithms in a distributed database.
• To analyze the efficiency of parallel algorithms.
Prerequisites:
• Knowledge of join and sort algorithms.
• Tools: Oracle Parallel Query.
Steps:
1. Set up Oracle Parallel Query.
2. Implement parallel join (e.g., hash join) and parallel sort (e.g., merge sort) algorithms.
3. Test the algorithms on large datasets.
4. Measure and compare execution times with sequential algorithms.
Expected Outcome:
• Working implementation of parallel join and sort in Oracle.
• Performance comparison report.

4. Implementation of Triggers and Assertion for Bank Database


Duration: 6 Hours
Objective:
• To implement triggers and assertions to enforce business rules in a bank database.
• To understand the use of triggers for automation and data integrity.
Prerequisites:
• Knowledge of SQL and database constraints.
• Tools: Oracle Database.
Steps:
1. Design a bank database schema (e.g., tables for accounts, transactions, customers).

2
2. Create triggers for events like balance updates, transaction logging, and overdraft prevention.
3. Implement assertions using Oracle constraints and triggers.
4. Test the triggers and assertions with sample data.
Expected Outcome:
• A bank database with working triggers and assertions in Oracle.
• Demonstration of trigger functionality (e.g., automatic logging of transactions).

5. Construction of Knowledge Database


Duration: 6 Hours
Objective:
• To build a knowledge database using ontologies and semantic web technologies.
• To understand the representation of knowledge in databases.
Prerequisites:
• Knowledge of ontologies and RDF (Resource Description Framework).
• Tools: Oracle Spatial and Graph.
Steps:
1. Define the domain and scope of the knowledge database (e.g., medical, educational).
2. Create an ontology using Protégé.
3. Populate the database with RDF data using Oracle Spatial and Graph.
4. Query the knowledge database using SPARQL.
Expected Outcome:
• A functional knowledge database with an ontology in Oracle.
• SPARQL queries demonstrating knowledge retrieval.

6. Study and Working of WEKA Tool


Duration: 5 Hours
Objective:
• To explore the WEKA tool for data mining and machine learning.
• To perform classification, clustering, and association rule mining.
Prerequisites:
• Basic understanding of data mining concepts.
• Tools: WEKA software.
Steps:
1. Install and set up WEKA.
2. Load a dataset (e.g., Iris dataset).

3
3. Perform classification using algorithms like J48 (decision tree).
4. Perform clustering using k-means.
5. Analyze the results and generate reports.
Expected Outcome:
• Hands-on experience with WEKA.
• Reports on classification, clustering, and association rule mining.

7. Query Processing – Implementation of Efficient Query Opti-


mizer
Duration: 4 Hours
Objective:
• To understand query processing and optimization techniques.
• To implement a simple query optimizer.
Prerequisites:
• Knowledge of query execution plans and indexing.
• Tools: Oracle Database.
Steps:
1. Write complex SQL queries.
2. Analyze the query execution plan using Oracle’s EXPLAIN PLAN.
3. Optimize the queries using indexing, rewriting, and hints.
4. Compare the performance before and after optimization.
Expected Outcome:
• Optimized SQL queries with improved performance in Oracle.
• Analysis of query execution plans.

8. Designing XML Schema for Company Database


Duration: 4 Hours
Objective:
• To design an XML schema for a company database.
• To understand the structure and validation of XML documents.
Prerequisites:
• Knowledge of XML and database schema design.
• Tools: Oracle XML DB.
Steps:
1. Identify the entities and relationships in the company database.

4
2. Design an XML schema (XSD) to represent the database.
3. Validate the schema using Oracle XML DB.
4. Query the XML data using XPath or XQuery.
Expected Outcome:
• A valid XML schema for a company database in Oracle.
• Sample XML documents and queries.

9. Implement Distributed Database for Bookstore


Duration: 3 Hours
Objective:
• To design and implement a distributed database for a bookstore.
• To understand data fragmentation, replication, and distributed query processing.
Prerequisites:
• Knowledge of distributed database concepts.
• Tools: Oracle Distributed Database.
Steps:
1. Design the bookstore database schema.
2. Fragment the database across multiple nodes using Oracle Distributed Database.
3. Implement distributed queries and transactions.
4. Test the system for consistency and performance.
Expected Outcome:
• A functional distributed database for a bookstore in Oracle.
• Demonstration of distributed query processing.

10. Deadlock Detection Algorithm for Distributed Database Us-


ing Wait-for Graph
Duration: 3 Hours
Objective:
• To implement a deadlock detection algorithm in a distributed database.
• To understand the concept of wait-for graphs.
Prerequisites:
• Knowledge of deadlocks and distributed systems.
• Tools: Oracle Database.
Steps:
1. Simulate a distributed database environment using Oracle.

5
2. Create a wait-for graph to represent resource allocation and requests.
3. Implement an algorithm to detect cycles in the wait-for graph.
4. Test the algorithm with sample data.

Expected Outcome:
• A working deadlock detection algorithm in Oracle.
• Demonstration of deadlock detection in a distributed system.

You might also like