Unit i Dbms Questions and Answers
Unit i Dbms Questions and Answers
Q2 DEFINE DBMS
A database management system (DBMS) is a software tool that allows users to store, manage, and retrieve data in a
database. DBMSs can be used to organize and access large amounts of data quickly and efficiently. They can also help
ensure data accuracy, availability, and accessibility.
15. Data organization: A DBMS provides a systematic approach to organizing data in a structured way.
Disadvantages of DBMS
1. Complexity
2. Size The functionality of DBMS makes use of a large piece of software which occupies megabytes of disk space.
3. Higher impact of a failure
4. Cost of DBMS The cost of DBMS varies significantly depending on the environment and functionality provided.
5. Regular updates
6. Staff Training and Expense
7. Cost of Data Conversion:
8. Unavailability: Distributed DBMS can be unavailable in case of system failure.
20 Capacity planning:
A database administrator has the responsibility of planning for increased capacity, in case of sudden growth in database need .
TCL is a language which manages the transactions within the database. It is used to execute the changes made by the data
manipulation language statements. The TCL commands are: Commit, Rollback.
Q6 Explain Data Base Users
A Database User is defined as a person who interacts with data daily, updating, reading, and modifying the given data. Databa se users can access and
retrieve data from the database through the Database Management System (DBMS) applications and interfaces.
Sophisticated Users
Sophisticated users can be engineers, scientists, business analyst, who are familiar with the database. They can develop thei r own database applications
according to their requirement. They don’t write the program code but they interact the database by wri ting SQL queries directly through the query
processor.
Application Programmers
Application Programmers also referred as System Analysts or simply Software Engineers, are the back-end programmers who writes the code for the
application programs. They are the computer professionals. These programs could be written in Programming langua ges such as Visual Basic, Developer, C,
FORTRAN, COBOL etc
Specialized users
Specialized users are sophisticated users who write specialized database application that does not fit into the traditional data-processing framework. Among
these applications are computer aided-design systems, knowledge-base and expert systems etc.
Data models are created using diagrams, symbols, and text, and they typically reflect business and application requirements. They can be created from scratch, or extracted
from existing systems through reverse-engineering. Data models are expected to change over time as business needs change.
Data Model gives us an idea that how the final system will look like after its complete implementation. It defines the data elements and the relationships between the data
elements.
Some types of data models:
• Relational model: The most common model, which organizes data into tables
• Hierarchical model: Organizes data in a tree-like structure with one-to-many relationships
• Network model: Similar to the hierarchical model, but allows many-to-many relationships between linked records
A hierarchical database model is a way to organize data in a tree-like structure, with records linked together by links
The main difference between this model and the hierarchical model is that any record can have several parents in the network model. It uses a graph instead of a
hierarchical tree.
Entity-Relationship Model or simply ER Model is a high-level data model diagram. In this model, we represent the real-world problem in the pictorial form to make it easy to
understand. It is also very easy for the developers to understand the system by just looking at the ER diagram.
ER diagram has the following three components:
• Entities: Entity is a real-world thing. It can be a person, place, or even a concept. Example: Teachers, Students, Course, Building, Department, etc are some of the
entities of a School Management System.
• Attributes: An entity contains a real-world property called attribute. This is the characteristics of that attribute. Example: The entity teacher has the property like
teacher id, salary, age, etc.
• Relationship: Relationship tells how two attributes are related. Example: Teacher works for a department.
Example:
In the above diagram, the entities are Teacher and Department. The attributes of Teacher entity are Teacher_Name, Teacher_id, Age, Salary, Mobile_Number. The attributes
of entity Department entity are Dept_id, Dept_name. The two entities are connected using the relationship. Here, each teacher works for a department.
Advantages of ER Model
• Simple: Conceptually ER Model is very easy to build. If we know the relationship between the attributes and the entities we can easily build the ER Diagram for the
model.
• Effective Communication Tool : This model is used widely by the database designers for communicating their ideas.
• Easy Conversion to any Model : This model maps well to the relational model and can be easily converted relational model by converting the ER model to the table.
This model can also be converted to any other model like network model, hierarchical model etc.
Disadvatages of ER Model
• No industry standard for notation: There is no industry standard for developing an ER model. So one developer might use notations which are not understood by
other developers.
• Hidden information: Some information might be lost or hidden in the ER model. As it is a high-level view so there are chances that some details of information
might be hidden.
• Bad Design: As the relational model is very easy to design and use. So the users don't need to know how the data is stored in order to access it. This ease of design
can lead to the development of a poor database which would slow down if the database grows.
Logical data independence is primarily used when we want to change the conceptual schema
without affecting the external programs
Physical data independence is primarily used to separate the conceptual level data from the
physical or internal levels. It is relatively easy to achieve and allows a user to change the physical
storage structure without affecting the conceptual schema.