Explain the following terms Domain, Tuple, Relation Attribute

1. A relation is a table with columns and rows.

2. An attribute is a named column of a relation.
3. A tuple is a row of a relation.
4. A domain is a set of allowable values for one or more attributes.

Explain difference between DMS and RDBMS

DBMS represents a Database Management System. It is used to create/update/delete

and maintain a database and it provides controlled access to data. RDBMS, Relational
Database Management System, is an enhanced version of DBMS.

Why is relational data model popular?

The Relational database became popular because of SQL and its programming
abstraction.

The other reason for the Relational databases' popularity is the simple data modeling
abstraction they provide. The Relational Model can easily map real-world use cases in
almost ninety percent of the cases. The table and column abstraction are easier to
grasp than other data modeling abstractions like objects and graphs.
Relational databases are just simpler to use, model and have established practices for
their management.

What are record based models?

High-level Conceptual Data Models - represents data as a hierarchical tree structure

Record-based Logical Data Models

1. The relational model - represents data as relations or tables.
2. Network model - represents data as record types. This model also represents a
limited type of one to many relationships called a set type.
3. Hierarchical model - represents data as a hierarchical tree structure. Each
branch of the hierarchy represents a number of related records.

How RDMS stores its data?

Database systems typically store data in fixed-size blocks called pages. The pages are
(should be) a multiple of the disk blocking factor. Recall that a disk is a 'block device'.
The disk is always going to read/write entire blocks, even if the read request is for some
smaller amount of data. IOW, if you call read() (in the C language) and request to read
100 sequential bytes of a file, the disk is going to read the entire block that contains the
100 bytes from the media into its cache, which will be copied into the file system's
cache, and 100 bytes of it will be copied into your program's buffer. So, database
system page sizes should be aligned to the disk blocking factor so that none of that I/O
is wasted. IOW, if the disk block size is 4K, it is inefficient to have a database page size
of 1K knowing that the disk is going to read/write 4K regardless. Make the database
page size a multiple of the file system block size (1X, 2X, ...).