Scribd
Upload
53 views

DBMS Important Questions

The document discusses key concepts in data modeling, SQL, transactions, keys and constraints, and database normalization. It covers topics such as conceptual, logical and physical data models, entity relationship diagrams, SQL commands, ACID properties, transactions, isolation levels, database normalization forms, and differences between SQL and NoSQL databases.

Uploaded by

Ritik Prajapati
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
53 views

DBMS Important Questions

The document discusses key concepts in data modeling, SQL, transactions, keys and constraints, and database normalization. It covers topics such as conceptual, logical and physical data models, entity relationship diagrams, SQL commands, ACID properties, transactions, isolation levels, database normalization forms, and differences between SQL and NoSQL databases.

Uploaded by

Ritik Prajapati
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 3

DATA MODELLING :

1. What is data modeling?

2. What are the objectives of data modeling?

3. What are the three levels of data modeling?

4. What is conceptual data model?

5. What is logical data model?

6. What is physical data model?

7. What is entity relationship diagram (ERD)?

8. What are the components of ERD?

9. What is normalization? What are the normal forms?

10. What is denormalization? When is it used?

SQL :

11. What is SQL?

12. What are the types of SQL commands?

13. What is the difference between WHERE and HAVING clause?

14. What is the difference between UNION and UNION ALL?

15. What is the difference between DELETE and TRUNCATE statements?

16. What is the difference between primary key and unique constraint?

17. What is a view? What are the benefits of views?

18. How to create a view?

19. What is a stored procedure? What are the benefits of stored procedures?

20. How to create a stored procedure?

TRANSACTION :

21. What is a transaction in DBMS?

22. What are the ACID properties of transactions?


23. What is a commit operation?

24. What is a rollback operation?

25. What is a deadlock in transactions?

26. What is a transaction log?

27. What is a savepoint in transactions?

28. What is concurrency control?

29. What are the types of transaction isolation levels?

30. What is two-phase locking (2PL) protocol?

KEYS AND CONSTRAINTS :

31. What is a transaction in DBMS?

32. What are the ACID properties of transactions?

33. What is a commit operation?

34. What is a rollback operation?

35. What is a deadlock in transactions?

36. What is a transaction log?

37. What is a savepoint in transactions?

38. What is concurrency control?

39. What are the types of transaction isolation levels?

40. What is two-phase locking (2PL) protocol?

Database Normalization:

41. What is database normalization?

42. What are the main objectives of normalization?

43. What is the First Normal Form (1NF)?

44. What is the Second Normal Form (2NF)?

45. What is the Third Normal Form (3NF)?

46. What is the Boyce-Codd Normal Form (BCNF)?


47. What is the Fourth Normal Form (4NF)?

48. What is the Fifth Normal Form (5NF)?

49. What is denormalization, and when is it used?

50. What are the advantages and disadvantages of normalization?

51. SQL v/s NoSQL, explains with a use case when to use what

Answer: SQL (Structured Query Language) and NoSQL (Not Only SQL) are two different types of
database management systems, each with its own strengths and best use cases. The choice between SQL
and NoSQL depends on various factors, including the nature of the data, scalability requirements, and the
specific use case. Let's explore both options and provide a use case for each.

SQL Databases: SQL databases are based on the relational model and use structured tables with
predefined schemas to store and organize data. They provide ACID (Atomicity, Consistency, Isolation,
Durability) properties, ensuring data integrity and transactional consistency. SQL databases are suitable
for scenarios where data relationships are well-defined and structured.

Use Case for SQL: An e-commerce website is a typical use case for an SQL database. The website requires
structured data such as customer information, orders, products, and inventory. These relationships can be
efficiently represented in tables and queried using SQL queries. The ACID properties of SQL databases
ensure that the transactions, such as placing an order or updating inventory, are processed reliably and
consistently.

NoSQL Databases: NoSQL databases, on the other hand, are designed to handle unstructured, semi-
structured, or rapidly changing data. They offer flexible schemas and are highly scalable and distributed.
NoSQL databases relax some of the traditional ACID properties to provide high availability and horizontal
scalability. There are different types of NoSQL databases, including key-value stores, document databases,
columnar databases, and graph databases, each optimized for specific use cases.

Use Case for NoSQL: A social media analytics platform is a good example of a use case that can benefit
from a NoSQL database. The platform collects and analyzes large volumes of unstructured data, such as
social media posts, user interactions, and engagement metrics. These data sources often have varying
formats and can change frequently. NoSQL databases, such as a document store or a graph database,
allow for flexible schema design and efficient storage and retrieval of unstructured data. The scalability
and distributed nature of NoSQL databases enable handling high data volumes and accommodating the
dynamic nature of social media data.

In summary, SQL databases are ideal for scenarios with structured data and well-defined relationships,
such as traditional business applications, while NoSQL databases are suitable for handling unstructured or
rapidly changing data, such as social media analytics, content management systems, or IoT applications.
The choice between SQL and NoSQL depends on the specific requirements and characteristics of your
data and use case.

You might also like