Scribd
Upload
2 views1 page

Dbms Index

The document outlines various database schemas for different applications, including student records, employee information, order management, insurance details, book dealership, student enrollment, and library management. Each schema specifies the entities, their attributes, and relationships. The document serves as a reference for designing relational databases in these contexts.

Uploaded by

ziyan.a.k456
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
2 views1 page

Dbms Index

The document outlines various database schemas for different applications, including student records, employee information, order management, insurance details, book dealership, student enrollment, and library management. Each schema specifies the entities, their attributes, and relationships. The document serves as a reference for designing relational databases in these contexts.

Uploaded by

ziyan.a.k456
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

INDEX

SL Page
Program Name Date Remarks
No No
A) Create the following relation for the student: Student (regno:string,name:
1. string, class: string, bdate: date, marks1:int, marks1:int, marks2:int, 17-02-26
marks3:int)
B) Consider the following database that maintain information about
employees & Departments. Employee (empid: int, ename: string, age:int, 24-02-26
salary:int, #deptno:int) Department (deptno:int, dname: string, #manager-id:
int)

2. Consider the following schema for OrderDatabase: SALESMAN 17-03-26


(Salesman_id, Name, City, Commission) CUSTOMER (Customer_id,
Cust_Name, City, Grade,Salesman_id) ORDERS (Ord_No, Purchase_Amt,
Ord_Date, #Customer_id, Salesman_id)

3. Consider the Insurances database The primary keys are underlined and the 31-03-26
data types are specified. PERSON (DRIVER-ID#: string, name: string,
address: string) CAR (Regno: string, model: string, year: int) ACCIDENT
(report-number: int, date: date, location: string) OWNS (#driver-id: string,
#Regno: string) PARTICIPATED (#driver-id: string, #Regno: string,
#report-number: int, Damage amount: int)

4. The following tables are maintained by a book dealer. AUTHOR (author- 14-04-26
id:int, name: string, city: string, country: string) PUBLISHER (publisher-id:
int, name: string, city: string, country: string) CATALOG (book-id: int, title:
string, author-id#: int, publisher-id#: int, category-id#: int, year: int, price:
int) CATEGORY (category-id: int, description: string) ORDER-DETAILS
(order-no: int, #book-id: int, quantity: int)

5. Consider the following database of student enrolment in courses and books 28-04-26
adopted each course. STUDENT (regno: string, name: string, major: string,
bdate: date) COURSE (course: int, cname: string, dept: string) ENROLL
(#regno: string, course#: int, sem:int marks: int) TEXT (book-ISBN : int,
book-title: string, publisher: string, author: string) BOOK_ADOPTION
(course#: int, sem: int, book-ISBN# : int)

6. Consider the following database for library management system BOOK 12-05-26
(Book_id , Title, Publisher_Name, Pub_Year) BOOK_AUTHORS
(#Book_id, Author_Name) PUBLISHER (Name, Address, Phone)
BOOK_COPIES (#Book_id, #Branch_id, No-of_Copies)
BOOK_LENDING (#Book_id, #Branch_id, Card_No, Date_Out,
Due_Date) LIBRARY_BRANCH (Branch_id, Branch_Name, Address)

Student Sign

You might also like