Describe Data vs Information
Describe Data vs Information
Data:
• Data refers to unprocessed facts and figures. It has no meaningful
context, and you cannot make your own decisions based on it. It
can be used in a variety of forms like numbers, characters,
symbols, images, etc.
• Information depends on data, as data becomes information when
it is analyzed, structured, or given context.
Example: 85, Fahath, 2025-04-05.
Information:
Example:
In an e-commerce website
The system stores customer orders, product details, and inventory.
The data is sorted into categories like customer info, products, and
orders, making it easy to manage.
Benefits:
• Makes it easy to find, update, and search for data.
• Helps avoid mistakes like sending the wrong item or charging
the wrong amount.
• Allows multiple workers to use the data at the same time.
• Information is easy to find, and everything stays secure and
organized.
• Buffer management
• Stored data manager
• DDL compiler
• Interactive query interface
• Query compiler
• Query optimizer
• Pre-compiler
• Runtime database processor
• System catalog
• Concurrency control system
• Backup and recovery system
Buffer management
Buffer management helps move data between the disk and the
computer’s memory (RAM). It keeps the data that is used often in
memory, so the system doesn’t have to read from the slower disk each
time. This makes the system faster and more efficient.
DDL compiler
The DDL compiler works with commands like CREATE, ALTER, and DROP
to make or change things like tables and indexes in the database. It keeps
track of these changes and helps make sure the database is set up
correctly.
Query Optimizer
The Query Optimizer is a part of the DBMS that makes SQL queries faster.
It looks at different ways to get the data and picks the best one, using the
least memory and processing power. This helps the system work more
efficiently, especially when dealing with a lot of data.
2-tier architecture
In 2-tier architecture, the client and server are separate. The client asks the
server for data, and the user interface is on the client’s machine. It's used for
small applications.
3-tier architecture
A 3-tier architecture divides the system based on how users use the data. It is
the most common design for database systems. The system has three layers:
1. Presentation layer
2. Application layer
3. Database Server