0% found this document useful (0 votes)
20 views7 pages

Question Paper - 1

The document is a question paper covering various topics in Database Management Systems (DBMS), including data independence, client/server architecture, and the differences between database approaches and traditional file systems. It includes questions on E-R modeling, normalization, transaction processing, and SQL queries. Each question is structured to assess understanding of key DBMS concepts and their applications.

Uploaded by

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

Question Paper - 1

The document is a question paper covering various topics in Database Management Systems (DBMS), including data independence, client/server architecture, and the differences between database approaches and traditional file systems. It includes questions on E-R modeling, normalization, transaction processing, and SQL queries. Each question is structured to assess understanding of key DBMS concepts and their applications.

Uploaded by

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

Question Paper - 1

Q.1.
(a) Explain Program Data Independence supported by DBMS. 03
(b)Explain two tier & three tier client/server architecture of DBMS in brief. 04
(c)Discuss the main characteristics of database approach and how it differs from
traditional file systems. 07

Q.2
(a) Compare Single,Multi-valued & Composite attributes in E-R Model 03
(b) Explain Cardinality Ratio & Participation constraint in E-R Modeling. 04
(c)Explain Three Layer Schema Architecture of DBMS. 07
OR
(c)Explain Following Constraints supported by DBMS:
1.Primary Key
2.Foreign Key / Referential Integrity Constraints
3. Not NULL 07
Q.3
(a)Consider a relation R(A,B,C,D,E) with following dependencies:
AB→C, CD→E, DE→B .
Is AB a candidate key of this relation? 03
(b)Explain Inference Rules for Functional Dependency. 04
(c)Explain Specialization, Generalization and Categorization in EER Modeling. 07
OR
Q.3
(a)Explain ACID Properties of transaction with appropriate example. 03
(b)Explain Update anomalies with example. 04
(c)Explain various types of JOIN operation in Relational Algebra. 07
Q.4
(a)Explain Cursors in PL/SQL with example. 03
(b)Explain Lost update & Dirty Read problem in Transaction Processing. 04
(c)Explain Normalization with 1NF, 2NF and 3NF in brief. 07
OR
Q.4
(a)Explain the Rollback and commit commands. 03
(b)Explain Triggers in PL/SQL with example. 04
(c)Explain working of two phase commit protocol. 07
Q.5
(a)What is Serial & Serializable Schedule in Transaction Processing. 03
(b)Explain state transition Diagram for Transaction Processing in DBMS. 04
(c)Explain Conflict Serializability with precedence graph in TransactionProcessing.07
OR
Q.5
(a)What is a query execution plan? 03
(b)Explain handling of aggregate functions with GROUP BY clouse in SQL. 04
(c)Consider Following 3 Tables for library database and Write SQL Queries. 07
1. Books ( BookID, BookTitle, Price, Author, Publisher )
2. Students (StudID, StudName, DOB, Gender, Branch, Sem, Address)
3. Issue_Books ( StudID, BookID, Issue_Date)
Query1: List all Books whose Title contains word ‘DBMS’.
Query2: Display all Publisher Name & Total Price of Books of that publisher.
Query3: Display list of all books which are not issued to any students.
Query4. Display the author name whose number of books is maximum in library.
Query5: Display all Books assigned to student with name “RAJESH”
Solution :

Q1. (a) Explain Program Data Independence supported by DBMS. 03

Data Independence in DBMS


Data independence is a crucial feature of a Database Management System (DBMS) that
allows changes to be made to the database schema at one level without affecting the schema
at the next higher level. This feature is essential for maintaining the flexibility and
adaptability of a database system.
Types of Data Independence

There are two main types of data independence:


a) Logical Data Independence
Logical data independence refers to the ability to change the conceptual schema without
altering the external schema. This means that modifications to the logical structure of the
database, such as adding or deleting entities or attributes, do not affect the user views or
application programs. Logical data independence is achieved at the user interface level and is
crucial for maintaining the separation between the external and conceptual levels of the
database.
For example, if a new attribute is added to a table in the conceptual schema, the external
schema (user views) remains unaffected.
b) Physical Data Independence
Physical data independence refers to the ability to change the internal schema without
affecting the conceptual schema. This means that changes to the physical storage of the data,
such as modifying the storage size or changing the file organization, do not impact the logical
structure of the database. Physical data independence is achieved at the logical interface level
and is essential for maintaining the separation between the conceptual and internal levels of
the database.
For example, changing the storage location of the database from one drive to another does not
affect the conceptual schema.
Importance of Data Independence

Data independence is vital for several reasons:


 Flexibility: It allows the database to adapt to changes without affecting the applications
that use it.
 Scalability: It enables the database to scale and accommodate new requirements without
disrupting existing operations.
 Maintainability: It simplifies the maintenance of the database by allowing changes to be
made at one level without impacting other levels
Q1. (b)Explain two tier & three tier client/server architecture of DBMS in brief. 04

2-Tier Architecture

In a 2-tier architecture, the application is divided into two layers: the client (front-end) and
the database server (back-end). The client directly communicates with the database server,
making this setup simpler and easier to implement. This architecture is suitable for smaller
applications with fewer users and straightforward data needs.
Characteristics:
 Client Tier: The user-facing component that includes the graphical user interface (GUI).
Users interact with this tier to enter, access, and manipulate data.
 Database Server Tier: Manages data storage, retrieval, and administration. It handles client
requests, performs database queries, and returns the required data.
Advantages:
 Simplicity: Easy to build and maintain.
 Performance: Direct communication between client and database reduces network
overhead.
Disadvantages:
 Scalability: Limited scalability due to tight coupling between client and database.
 Security: Less secure as the client has direct access to the database.
3-Tier Architecture

In a 3-tier architecture, the application is divided into three layers: the presentation tier (front-
end), the application tier (middle-tier), and the data tier (back-end). This architecture
introduces an intermediate layer, the application server, which handles business logic
separately from the client and database.
Characteristics:
 Presentation Tier: The user interface and communication layer where users interact with
the application. Developed using HTML, CSS, and JavaScript for web applications.
 Application Tier: The logic tier that processes information collected from the presentation
tier using business logic. Developed using languages like Python, Java, or PHP.
 Data Tier: The database tier where information is stored and managed. Uses relational
databases like MySQL or NoSQL databases like MongoDB.
Advantages:
 Scalability: Highly scalable as each layer can be scaled independently.
 Security: Enhanced security as the presentation and data tiers cannot communicate directly.
 Maintainability: Easier to maintain and update, with changes often isolated to one layer.
Disadvantages:
 Complexity: More complex to build and maintain compared to 2-tier architecture.
The choice between 2-tier and 3-tier architecture depends on the size and complexity of our
application. 2-tier architecture is ideal for smaller, simpler applications with fewer users,
while 3-tier architecture is better suited for larger, more complex applications that require
scalability, security, and maintainability.
Q1. C.
Discuss the main characteristics of database approach and how it differs from
traditional file systems.

A File System and a Database Management System (DBMS) are two different approaches
to managing and organizing data. Each has its own set of features, advantages, and use cases.
File System

A File System is a method of organizing and storing files on a storage medium like a hard
disk, pen drive, or DVD. It provides basic operations such as creating, deleting, renaming,
and accessing files. Files are typically organized in a hierarchical structure, with directories
and subdirectories. Examples of file systems include NTFS (New Technology File System)
and EXT (Extended File System).
 Data Redundancy: Redundant data can be present, leading to inconsistencies.
 Backup and Recovery: Lacks built-in mechanisms for backup and recovery.
 Query Processing: No efficient query processing capabilities.
 Security: Provides less security compared to DBMS.
 Cost: Generally less expensive than DBMS.
 User Access: Typically allows only one user to access data at a time.
DBMS (Database Management System)

A DBMS is a software application designed to manage large amounts of structured data. It


provides advanced functionalities such as querying, indexing, transactions, and data integrity.
Examples of DBMS include Oracle, MySQL, and MS SQL Server.
 Data Redundancy: Eliminates redundant data through normalization.
 Backup and Recovery: Provides in-house tools for backup and recovery.
 Query Processing: Efficient query processing using SQL.
 Security: Offers robust security mechanisms.
 Cost: Generally more expensive than file systems.
 User Access: Supports multiple users accessing data simultaneously.
The characteristics of the database technique in DBMS are

1. Data Independence – Physical data storage can change without affecting how data is
logically organized, making systems more flexible.
2. Data Integration – Combines data from different sources into one database, reducing
duplication and improving consistency.
3. Centralized Control – Data is managed from a single point, simplifying security, backup,
and user access management.
4. Consistency – Data is stored in a uniform and predictable format using constraints,
ensuring accurate and reliable data.
5. Scalability – Databases can efficiently handle growing amounts of data, suitable for both
small and large applications.
6. Security – Access controls and encryption protect data from unauthorized users, ensuring
privacy and safety.
7. Concurrent Access – Multiple users can access and work with data at the same time, with
controls to prevent conflicts.
8. Data Modeling – Helps design a clear and logical structure of data using entities,
attributes, and relationships.
9. Data Integrity – Ensures data accuracy and valid relationships through rules like primary
keys and foreign keys.
10. Data Querying – SQL allows users to search, filter, sort, and analyze data easily and
efficiently.
11. Backup & Recovery – Regular backups allow data to be restored in case of loss or
system failure.
12. Data Replication – Copies data to multiple servers to improve availability and ensure
access during server failures.

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy