unit 2 rm
unit 2 rm
1. Attribute: Each column in a Table. Attributes are the properties which define a relation. e.g.,
Student_Rollno, Name, etc.
2. Tables – In the Relational model the, relations are saved in the table format. It is stored along
with its entities. A table has two properties rows and columns. Rows represent records and
columns represent attributes.
3. Tuple – It is nothing but a single row of a table, which contains a single record.
4. Relation Schema: A relation schema represents the name of the relation with its attributes.
5. Degree: The total number of attributes which in the relation is called the degree of the relation.
6. Cardinality: Total number of rows present in the Table.
7. Column: The column represents the set of values for a specific attribute.
8. Relation instance – Relation instance is a finite set of tuples in the RDBMS system. Relation
instances never have duplicate tuples.
9. Relation key – Every row has one, two or multiple attributes, which is called relation key.
10. Attribute domain – Every attribute has some pre-defined value and scope which is known as
attribute domain.
Relational Integrity Constraints
Relational Integrity constraints in DBMS are referred to conditions which must be present for a valid relation.
These Relational constraints in DBMS are derived from the rules in the mini-world that the database
represents.
There are many types of Integrity Constraints in DBMS. Constraints on the Relational database management
system is mostly divided into three main categories are:
1. Domain Constraints
2. Key Constraints
3. Referential Integrity Constraints
Domain Constraints
Domain constraints can be violated if an attribute value is not appearing in the corresponding domain or it is
not of the appropriate data type.
Domain constraints specify that within each tuple, and the value of each attribute must be unique. This is
specified as data types which include standard data types integers, real numbers, characters, Booleans,
variable length strings, etc.
Key Constraints
An attribute that can uniquely identify a tuple in a relation is called the key of the table. The value of the
attribute for different tuples in the relation has to be unique.
Example:
2 Amazon Active
3 Apple Inactive
In the given table, CustomerID is a key attribute of Customer Table. It is most likely to have a single key
for one customer, CustomerID =1 is only for the CustomerName =” Google”.
Example:
Tuple for CustomerID =1 is referenced twice in the relation Billing. So we know CustomerName=Google
has billing amount $300
Insert Operation
The insert operation gives values of the attribute for a new tuple which should be inserted into a relation.
Update Operation
You can see that in the below-given relation table CustomerName= „Apple‟ is updated from Inactive to
Active.
Delete Operation
To specify deletion, a condition on the attributes of the relation selects the tuple to be deleted.
The Delete operation could violate referential integrity if the tuple which is deleted is referenced by foreign
keys from other tuples in the same database.
Select Operation
In the above-given example, CustomerName=”Amazon” is selected
Few relational databases have limits on field lengths which can‟t be exceeded.
Relational databases can sometimes become complex as the amount of data
grows, and the relations between pieces of data become more complicated.
Complex relational database systems may lead to isolated databases where the
information cannot be shared from one system to another.