Guru Nanak Dev Engineering College, Ludhiana
Department of Information Technology
Billing Software System
Mini Project Report
Submitted by:
Jaya Subedi
Roll Number: 2303001
Session: 2024–2025
Under the Guidance of:
Mrs.Reema Verma
June 20, 2025
CERTIFICATE
This is to certify that the mini project report titled “Event Management System”
has been completed successfully by Nimrat Chandel/Jaya Subedi, Roll Number
2303030/2303001, under my guidance for the partial fulfillment of the requirements
of the course Database Management Systems (DBMS) at Guru Nanak Dev Engineering
College, Ludhiana.
Dr. Mohanjit Kaur Kang
Assistant Professor
Department of Information Technology
GNDEC, Ludhiana
Billing Software System GNDEC, Ludhiana
Contents
1 Introduction 3
2 Objective 3
3 Tools and Software Used 3
3.1 MySQL 8.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
3.2 MySQL Workbench . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
3.3 SQL Language . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
4 Database Design 4
4.1 Entity Relationship Diagram . . . . . . . . . . . . . . . . . . . . . . . . . 4
4.2 Table Structures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
4.2.1 Events Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
4.2.2 Participants Table . . . . . . . . . . . . . . . . . . . . . . . . . . 4
5 Implementation (SQL Queries) 4
5.1 Creating Database and Tables . . . . . . . . . . . . . . . . . . . . . . . . 5
5.2 Inserting Sample Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
5.3 Basic Query Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
5.4 Aggregate Functions and Grouping . . . . . . . . . . . . . . . . . . . . . 6
5.5 Advanced Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
6 Output Analysis 7
6.1 Event Listing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
6.2 Participant Distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
7 Conclusion 8
8 Future Scope 8
Page 2
Billing Software System GNDEC, Ludhiana
1 Introduction
The Event Management System is a database project designed to maintain records of
events and participants efficiently. In educational institutions and organizations, man-
aging various activities such as fests, exhibitions, seminars, and workshops requires sys-
tematic storage and retrieval of information. This system provides a relational database
solution that helps organizers track events and registrations.
The database architecture follows a simple yet effective relational model with two
primary entities: Events and Participants. The relationship between them is estab-
lished using foreign key constraints to maintain data integrity and consistency. This
project implements fundamental SQL operations to demonstrate the practical applica-
tion of database management concepts.
2 Objective
The main objectives of this Event Management System database project are:
• To create a relational database for organizing event and participant data efficiently
• To implement SQL operations including SELECT, INSERT, JOIN, and GROUP
BY queries
• To maintain referential integrity between events and participants using foreign key
constraints
• To demonstrate data manipulation and retrieval from related tables
• To create a practical database application that can be extended for real-world use
3 Tools and Software Used
3.1 MySQL 8.0
MySQL 8.0 was used as the primary database management system for this project. It
offers robust features for creating and managing relational databases, including support
for foreign key constraints, transactions, and various SQL operations.
3.2 MySQL Workbench
MySQL Workbench provided a graphical interface for database design, development, and
administration. It facilitated the creation of tables, relationships, and the execution of
SQL queries.
3.3 SQL Language
Standard SQL was used for all database operations, including:
• Data Definition Language (DDL) statements for creating and modifying database
objects
Page 3
Billing Software System GNDEC, Ludhiana
• Data Manipulation Language (DML) statements for inserting and retrieving data
• Data Control Language (DCL) statements for managing database access
4 Database Design
4.1 Entity Relationship Diagram
The database consists of two primary entities with a one-to-many relationship:
• Events: Contains information about various events organized
• Participants: Stores details of individuals registered for events
Each event can have multiple participants, while each participant is registered for one
specific event.
4.2 Table Structures
4.2.1 Events Table
Column Data Type Description
event id INT Primary Key (Auto Increment)
event name VARCHAR(100) Name of the event
event date DATE Date when the event is scheduled
venue VARCHAR(150) Location where the event will be held
organizer VARCHAR(100) Name of the event organizer (added
later)
Table 1: Structure of Events Table
4.2.2 Participants Table
Column Data Type Description
participant id INT Primary Key (Auto Increment)
name VARCHAR(100) Name of the participant
email VARCHAR(100) Email address for communication
phone VARCHAR(15) Contact number
event id INT Foreign Key referencing
events(event id)
registration time TIMESTAMP Time when registration was recorded
Table 2: Structure of Participants Table
5 Implementation (SQL Queries)
The implementation phase involved creating the database schema and writing SQL
queries to perform various operations.
Page 4
Billing Software System GNDEC, Ludhiana
5.1 Creating Database and Tables
USE event_management ;
-- Creating ’ events ’ table
CREATE TABLE events (
event_id INT AUTO_INCREMENT PRIMARY KEY ,
event_name VARCHAR (100) NOT NULL ,
event_date DATE NOT NULL ,
venue VARCHAR (100) NOT NULL
);
-- Creating ’ participants ’ table
CREATE TABLE participants (
participant_id INT AUTO_INCREMENT PRIMARY KEY ,
name VARCHAR (100) NOT NULL ,
email VARCHAR (100) ,
phone VARCHAR (15) ,
event_id INT ,
registrati on_tim e TIMESTAMP DEFAULT CURRENT_TIMESTAMP ,
FOREIGN KEY ( event_id ) REFERENCES events ( event_id )
);
Listing 1: Creating Database and Tables
5.2 Inserting Sample Data
-- Inserting events
INSERT INTO events ( event_name , event_date , venue )
VALUES
( ’ Youth Fest ’ , ’ 2025 -04 -20 ’ , ’ Auditorium ’) ,
( ’ Art Exhibition ’ , ’ 2025 -05 -01 ’ , ’ Gallery Hall ’) ,
( ’ Anand Utsav ’ , ’ 2025 -05 -15 ’ , ’ Open Air Theatre ’) ,
( ’ Tech Symposium ’ , ’ 2025 -06 -10 ’ , ’ Main Conference Hall ’) ,
( ’ Music Night ’ , ’ 2025 -06 -25 ’ , ’ Auditorium ’) ;
-- Inserting participants
INSERT INTO participants ( name , email , phone , event_id )
VALUES
( ’ Nimrat Chandel ’ , ’ nimrat@gmail . com ’ , ’ 9876543210 ’ , 1) ,
( ’ Jaya Subedi ’ , ’ jaya@gmail . com ’ , ’ 9876500011 ’ , 2) ,
( ’ Siya Kaur ’ , ’ siya@gmail . com ’ , ’ 9876500099 ’ , 1) ,
( ’ Rohit Mehta ’ , ’ rohit@gmail . com ’ , ’ 9988776655 ’ , 4) ,
( ’ Tanya Sharma ’ , ’ tanya@gmail . com ’ , ’ 9876001122 ’ , 3) ,
( ’ Aditya Singh ’ , ’ aditya@gmail . com ’ , ’ 9876500022 ’ , 5) ,
( ’ Neha Verma ’ , ’ neha@gmail . com ’ , ’ 9876002211 ’ , 1) ;
Listing 2: Inserting Sample Data
Page 5
Billing Software System GNDEC, Ludhiana
5.3 Basic Query Operations
-- View all events
SELECT * FROM events ;
-- View all participants
SELECT * FROM participants ;
-- Join participants with event details
SELECT
p . name AS participant_name ,
p . email ,
e . event_name ,
e . event_date ,
p . regist ration _time
FROM participants p
JOIN events e ON p . event_id = e . event_id ;
Listing 3: Basic Query Operations
5.4 Aggregate Functions and Grouping
-- Count of participants for each event
SELECT
e . event_name ,
COUNT ( p . participant_id ) AS t ota l_ pa rt ic ip an ts
FROM events e
LEFT JOIN participants p ON e . event_id = p . event_id
GROUP BY e . event_id ;
Listing 4: Aggregate Functions and Grouping
5.5 Advanced Operations
-- Upcoming events ( after current date )
SELECT * FROM events
WHERE event_date > CURDATE ()
ORDER BY event_date ASC ;
-- List participants with email IDs missing
SELECT * FROM participants
WHERE email IS NULL OR email = ’ ’;
-- Alter table : Add a new column to events table
ALTER TABLE events ADD COLUMN organizer VARCHAR (100) ;
-- Modify column : Change venue column size
ALTER TABLE events MODIFY venue VARCHAR (150) ;
-- Create a VIEW
Page 6
Billing Software System GNDEC, Ludhiana
CREATE VIEW pa rticip ant_ev ent AS
SELECT
p . name AS participant_name ,
p . email ,
e . event_name ,
e . event_date
FROM participants p
JOIN events e ON p . event_id = e . event_id ;
-- Subquery : Find events where number of participants > 2
SELECT event_name FROM events
WHERE event_id IN (
SELECT event_id FROM participants
GROUP BY event_id
HAVING COUNT ( participant_id ) > 2
);
Listing 5: Advanced Operations
6 Output Analysis
6.1 Event Listing
The basic query to retrieve all events returns the following results:
• Event ID: 1, Name: Youth Fest, Date: 2025-04-20, Venue: Auditorium
• Event ID: 2, Name: Art Exhibition, Date: 2025-05-01, Venue: Gallery Hall
• Event ID: 3, Name: Anand Utsav, Date: 2025-05-15, Venue: Open Air Theatre
• Event ID: 4, Name: Tech Symposium, Date: 2025-06-10, Venue: Main Conference
Hall
• Event ID: 5, Name: Music Night, Date: 2025-06-25, Venue: Auditorium
6.2 Participant Distribution
The query counting participants per event shows:
• Youth Fest: 3 participants
• Art Exhibition: 1 participant
• Anand Utsav: 1 participant
• Tech Symposium: 1 participant
• Music Night: 1 participant
This analysis reveals that the Youth Fest is the most popular event with 3 registra-
tions, while other events have equal participation levels.
Page 7
Billing Software System GNDEC, Ludhiana
7 Conclusion
The Event Management System project successfully demonstrates the application of
database management concepts in a practical scenario. The implementation shows how
relational databases can efficiently organize and retrieve information about events and
participants.
Key achievements of this project include:
• Creation of a normalized database structure with proper relationships
• Implementation of various SQL operations including joins, aggregations, and sub-
queries
• Development of views for simplified data access
• Implementation of data integrity constraints using foreign keys
This project serves as a foundation for understanding how database systems can be
leveraged to solve real-world information management problems.
8 Future Scope
The current implementation of the Event Management System can be extended in several
ways:
• Additional Features: Implementing event categories, ticket types, payment track-
ing, and attendance management
• User Authentication: Adding a user login system with different access levels for
administrators and participants
• Web Interface: Developing a full-fledged web application with forms for event
creation and participant registration
• Payment Integration: Implementing payment gateway integration for paid events
• Reporting Module: Creating advanced reporting capabilities for event analytics
• Mobile Application: Developing a companion mobile app for participants to
register and track events
• Notification System: Adding automatic email or SMS notifications for event
updates
These enhancements would transform the current database project into a compre-
hensive event management solution suitable for large-scale deployment in educational
institutions and organizations.
Page 8
