Scribd
Upload
91 views9 pages

Booking Database Schema Overview

The document describes the structure of 15 database tables with their primary keys, foreign keys, field names, data types, and descriptions. The tables store information about bus details, customer bookings, employees, tour packages, hotel bookings, theater details, customer registration, and weather data.

Uploaded by

kalaivani
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
91 views9 pages

Booking Database Schema Overview

The document describes the structure of 15 database tables with their primary keys, foreign keys, field names, data types, and descriptions. The tables store information about bus details, customer bookings, employees, tour packages, hotel bookings, theater details, customer registration, and weather data.

Uploaded by

kalaivani
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd

TABLES

TABLE DESIGN
TABLE NAME : Busdetails
PRIMARY KEY : Bcount.

FIELD NAME DATA TYPE DESCRIPTION


Bcount Int Bus count
bname Varchar Bus name
seats Int Total seats
ac Varchar Ac
busno Varchar Bus no
busimage Image Bus image

TABLE NAME : Customizedbooing


PRIMARY KEY : bookingno

FIELD NAME DATA TYPE DESCRIPTION


bookingno Int Purchase id
cname Varchar Customer name
Insti Varchar Institution
address Varchar Address
contactno Varchar Contact no
Pickup Varchar Place
source Double Source
destination DateTime Destination
Places Varchar Places
Jdate Date time Journey date
Tdays Int Total days
Busno Int Bus no
Busname Varchar Bus name
initialamount Double Initial amount

TABLE NAME : employee


PRIMARY KEY : eid
FIELD NAME DATA TYPE DESCRIPTION
Eid Int Employee id
ename Varchar Employee name
gender Varchar Gender
age Int Age
address Varchar Address
contactno Varchar Contact no
bsalary Varchar Basic salary
TABLE NAME : featuretour
Primary key : packno

FIELD NAME DATA TYPE DESCRIPTION


Packno Int Package no
Ptype Varchar Package type
zone Varchar Zone
place Varchar Place
placeImage Image Image
fare Double Fare
aboutplace Varchar Place description

TABLE NAME : featuretourbooking


PRIMARY KEY : bookingno
FIELD NAME DATA TYPE DESCRIPTION
Bookingno Int Booking no
Cname Varchar Name
ptype Varchar Package type
zone Varchar Zone
totalmembers Int Total members
totalfare Double Total fare
jdate Date time Journey date
bookeddate Date time Booking date

TABLE NAME : feedback


FIELD NAME DATA TYPE DESCRIPTION
Cname Varchar Customer name
address Varchar Address
contactno Varchar Contact no
city Varchar City
gname Varchar Guide name
feedback Varchar Feedback
comments Varchar comments

TABLE NAME : Guideallocation


Foreign key : empid
FIELD NAME DATA TYPE DESCRIPTION
empid Varchar Employee id
empname Varchar Name
L1 Varchar Language 1
L2 Varchar Language 2
L3 Varchar Language 3
L4 Varchar Language 4
L5 Varchar Language 5
L6 Varchar Language 6
workingin Varchar Working in
TABLE NAME : hotelbooking
Foreign key : Bno
FIELD NAME DATA TYPE DESCRIPTION
Bno Int Booking no
Place Varchar Place
hname Varchar Hotel name
rtype Varchar Room type
ac Varchar Ac
dayrent Double Per day rent
tamount Double Total amount
cname Varchar Customer name
Bdate Date time Booking date
Fromdate Date time From date
Todate Date time To date

TABLE NAME : hoteldetails


Foreign key : hotelid
FIELD NAME DATA TYPE DESCRIPTION
Hotelid Int Hotel id
hname Varchar Hotel name
himage Image Image
Zone Varchar Zone
place Varchar Place
descr Double Description
TABLE NAME : hoteldetails
Foreign key : hotelid
FIELD NAME DATA TYPE DESCRIPTION
Bno Int Booking no
tname Varchar Theater name
fname Varchar Film name
cname Varchar Customer name
fc Varchar First class
Sc Varchar Second class
Totalseats Int Total seats
Bookdate Date time Booking date
Showtime Varchar Show time
showdate Date time Show date

TABLE NAME : register


Primary key : regid
FIELD NAME DATA TYPE DESCRIPTION
regid Int Registration id
cname Varchar Customer name
address Varchar Address
contactno Varchar Contact no
city Varchar City
secquestion Varchar Secret question
secanswer Varchar Secret answer
loginid Varchar Login id
pwd Varchar Password
Repwd Varchar Retype password
Regdate Date time Register date
emailid Varchar Email id
TABLE NAME : roomdetails
Foreign key : hotelid
FIELD NAME DATA TYPE DESCRIPTION
Hotelid Int Hotel id
Hname Varchar Hotel name
type Varchar Type
ac Varchar Ac
perdayRent Double Per day rent

TABLE NAME : theaterdetails


Foreign key : tno
FIELD NAME DATA TYPE DESCRIPTION
Tno Int Theater no
tname Varchar Theater name
timage Varchar Theater image

TABLE NAME : theaterdetails


Foreign key : tno
FIELD NAME DATA TYPE DESCRIPTION
Tno Int Theater no
tname Varchar Theater name
timage Varchar Theater image
TABLE NAME : tourpackage
Foreign key : packno
FIELD NAME DATA TYPE DESCRIPTION
Packno Int Package no
Source Varchar Source
Desti Varchar Destination
Place Varchar Place
Placeimage Image Image
Bname Varchar Bus name
Fare Double Fare
Tseats Int Total seats
date Date time Date
Depttime Varchar Departure time
duration Varchar duration
TABLE NAME : tourbooking
Primary key : bno
FIELD NAME DATA TYPE DESCRIPTION
bno Int booking no
Source Varchar Source
Desti Varchar Destination
places Varchar Place
cname Varchar Customer name
jdate Date time Journey date
Fare Double Fare
Tseats Int Total seats
totalamount Double Total amount
Depttime Varchar Departure time
Bookingdate Varchar Booking date
Guide Varchar Guide
Regid Varchar Register id
packageno Varchar Package no

TABLE NAME : weather


Foreign key : city
FIELD NAME DATA TYPE DESCRIPTION
City Varchar City
Sunny Varchar Sunny
Rainy Varchar Rainy
humidity Varchar humidity

Common questions

Powered by AI

Journey and fare calculation are systematically recorded across several tables. The 'tourbooking' table encapsulates the entire booking transaction, recording vital details such as source, destination, journey date, total fare, and total amount . The 'featuretourbooking' table also supports journey date tracking and the calculation of total fare based on the number of members and the package type . Calculations are presumably performed using backend application logic that utilizes these tables to provide accurate fees and journey information to customers during and after the booking process.

The database manages relationships between tour packages, buses, and customers primarily through linked tables and foreign keys. The 'tourpackage' table connects bus details with tour destinations and package specifics through the inclusion of fields like 'Bname' (Bus name) and fare . The 'featuretourbooking' and 'tourbooking' tables relate customers to tour package information, capturing connections between package numbers, booking details, and customer identities . This ensures coordinated access to relevant data across different domains, allowing for comprehensive management of customer journeys and services.

The database design accommodates tour bookings through multiple tables that store detailed information about different aspects of the tours and bookings. The 'featuretour' table holds information about different packages, including the package number, type, zone, place, and fare . The 'featuretourbooking' table links customers to specific tours, capturing booking numbers, customer names, package types, zones, total members, and fare. It also records journey dates and booking dates . Furthermore, tables such as 'tourpackage' and 'tourbooking' track specific package details including destinations, bus names, and departure times, along with booking specifics such as customer names, journey dates, and guide allocations .

The hotel booking system is structured using tables such as 'hotelbooking' and 'hoteldetails', where attributes like booking number, customer name, hotel name, room types, and dates of reservation are stored . This structure supports detailed management of bookings. However, potential data redundancy issues may arise due to the duplication of hotel-specific attributes across tables, like repeating hotel names or room types without careful use of foreign keys and normalization principles. Implementing references to 'hoteldetails' in other booking tables rather than directly storing repeated values could mitigate such redundancies.

The 'weather' table, which includes attributes for city-specific weather conditions like sunny, rainy, and humidity levels, can significantly influence tour operations and customer satisfaction . Real-time integration of this data into scheduling and operational planning can allow tour operators to anticipate and mitigate risks associated with adverse weather conditions, such as ensuring appropriate gear or rerouting tours. By providing proactive notifications to customers about weather conditions, customer experiences can be optimized, enhancing safety and preparing travelers, thus boosting satisfaction and trust in the service.

The design includes several elements aimed at securing customer data during the registration process. In the 'register' table, sensitive information, such as login credentials (loginid, pwd, Repwd), and personal security questions and answers (secquestion, secanswer) are stored . Best practices would suggest hashing passwords, enforcing strong password rules, and ensuring secure connections (e.g., HTTPS) during data entry to protect sensitive information from unauthorized access. Furthermore, storing only necessary data, maintaining strong database access controls, and regular security audits are recommended strategies for enhancing overall data privacy and security.

The 'Guideallocation' table supports multilingual guide allocations, listing multiple languages (L1-L6) that guides can speak, thereby enabling dynamically matching guides with customers based on language preferences . To facilitate this process, the database could integrate with customer preferences from booking tables, selecting and allocating guides whose language skills align with the customer's preferred language, enriching customer service. Additionally, the system could flag preferred languages as a requirement during booking processes, ensuring that multi-linguistic service is systematically available, improving overall cultural accommodation and customer satisfaction.

Storing images directly in databases as blobs can provide centralized management and easy association with specific records, such as linking tour images to 'tourpackage' entries and hotel images to 'hoteldetails' . This centralization aids in enhanced consistency and security under a single management system. However, it may also lead to increased storage needs and affect performance due to the typically sizeable nature of image files. An alternative approach might involve storing image file paths or URLs, optimizing database size and performance while still maintaining linkage to the visual data through external file systems.

Primary keys ensure that each record in a database table is unique, preventing duplicate entries and serving as a reliable identifier for each row. For instance, 'bookingno' is used as the primary key in the 'featuretourbooking' table to uniquely identify each booking . Foreign keys, on the other hand, are used to establish relationships between tables by linking a primary key from one table to another, maintaining referential integrity. For example, 'empid' acts as a foreign key in the 'Guideallocation' table to reference employee records, ensuring that only valid employees can be allocated as guides .

Customer feedback can be analyzed and integrated to refine services through structured data collection and assessment tools. The 'feedback' table, which logs customer names, contact information, guide names, and detailed feedback comments, serves as a critical source of insights into customer experiences . By regularly reviewing these entries, management can identify recurring issues, preferences for guides or tours, and opportunities for service enhancements. Further integration involves using this feedback data to adjust operational aspects such as guide allocations, tour packages, and even employee training programs, directly influencing changes within the database structure for more responsive customer service.

You might also like