Bhujbal Knowledge City
MET Institute of Technology-Polytechnic
Relational Data model
2.1Fundamentals of RDBMS- Record, fields, data types, tables and database.
2.2 Concept of RDBMS, E.F. Codd'a Rule for RDBMS,
2.2 Candidate key, Primary key, Foreign key.
2.3 Normalization concepts, Need of Normalization
2.3 Types of Normalization-1NF, 2NF, 3NF
2.4 Introduction to SQL, Data types in SQL,
2.4 Components of SQL - DDL,DML, DCL, DQL.
2.5 DDL Commands: CREATE,ALTER, DROP, TRUNCATE, DESC, RENAME.
2.6 Data Integrity constraints: Types - Primary key, Foreign key, Unique key constraint,
2.6 Buisness Rule Constraint- Null, Not Null & check constraint.
2.7 DML Commands: INSERT, UPDATE, DELETE
2.8 DCL Commands: COMMIT, SAVEPOINT, ROLLBACK, GRANT, REVOKE
2.9 DQL Commands: SELECT.
2.10 SQL Operators: Arithmatic, Comparison, Logical
2.10 Set, Range Searching operator- Between
2.10 Pattern matching operators- Like.
Prepared by: Prof. P. B. Khairnar
,2.1 Record, fields, tables and database
• Record (Tuple)- Tuple is single row of the table. A
tuple is a ordered set of attribute values.
• Field (attribute)- At is a column of the table,
attributes are known as fields.
• Tables- Relational model refers table as its basic
unit. It is combination of rows and columns.
• Database – It is considered as collection of tables.
Prepared by: Prof. P. B. Khairnar
, 2.2 E. F. Codd’s 12 Rules
1. The Information rule: All information in an RDBMS is represented
logically in just one way - by values in tables.
2. The Guaranteed Access rule: Each item of data in an RDBMS is
guaranteed to be logically accessible by resorting to a combination of
table name, primary key value, and column name.
3. The Systematic Treatment of Null Values rule: Null values (distinct
from an empty character string or a string of blank characters and
distinct from zero or any other number) are supported in a fully
relational DBMS for representing missing
4. The Dynamic Online Catalog Based on the Relational Model rule:
The database description is represented at the logical level in the same
way as ordinary data, so that authorized users can apply the same
relational database.
5. The Comprehensive Data Sublanguage rule: A relational system
may support several languages and various modes of terminal for data
definition, view definition, data manipulation etc.
6. The View Updating rule: All views of the data which are
theoretically updatable must be updatable in practice by the DBMS.
Prepared by: Prof. P. B. Khairnar
, 7. The High-level Insert, Update, and Delete rule: The capability of
handling a base relation or a derived relation as a single database to
perform all DML operations.
8. The Physical Data Independence rule: Application programs and
terminal activities remain logically unchanged whenever any changes
are made in either storage representations or access methods.
9. The Logical Data Independence rule: Application programs and
terminal activities remain logically unchanged when information
preserving changes of any kind are made to the base tables.
10. The Integrity Independence rule: Integrity constraints must be
definable in the RDBMS sub-language and stored in the system
catalogue and not within individual application programs.
11. The Distribution Independence rule: An RDBMS has distribution
independence. Distribution independence implies that users should
not have to be aware of whether a database is distributed.
12. The No subversion rule: If the database has any means of handling
a single record at a time that low-level language must not be able
avoid the integrity rules which are expressed in a higher-level language
that handles multiple records at a time.
Prepared by: Prof. P. B. Khairnar
MET Institute of Technology-Polytechnic
Relational Data model
2.1Fundamentals of RDBMS- Record, fields, data types, tables and database.
2.2 Concept of RDBMS, E.F. Codd'a Rule for RDBMS,
2.2 Candidate key, Primary key, Foreign key.
2.3 Normalization concepts, Need of Normalization
2.3 Types of Normalization-1NF, 2NF, 3NF
2.4 Introduction to SQL, Data types in SQL,
2.4 Components of SQL - DDL,DML, DCL, DQL.
2.5 DDL Commands: CREATE,ALTER, DROP, TRUNCATE, DESC, RENAME.
2.6 Data Integrity constraints: Types - Primary key, Foreign key, Unique key constraint,
2.6 Buisness Rule Constraint- Null, Not Null & check constraint.
2.7 DML Commands: INSERT, UPDATE, DELETE
2.8 DCL Commands: COMMIT, SAVEPOINT, ROLLBACK, GRANT, REVOKE
2.9 DQL Commands: SELECT.
2.10 SQL Operators: Arithmatic, Comparison, Logical
2.10 Set, Range Searching operator- Between
2.10 Pattern matching operators- Like.
Prepared by: Prof. P. B. Khairnar
,2.1 Record, fields, tables and database
• Record (Tuple)- Tuple is single row of the table. A
tuple is a ordered set of attribute values.
• Field (attribute)- At is a column of the table,
attributes are known as fields.
• Tables- Relational model refers table as its basic
unit. It is combination of rows and columns.
• Database – It is considered as collection of tables.
Prepared by: Prof. P. B. Khairnar
, 2.2 E. F. Codd’s 12 Rules
1. The Information rule: All information in an RDBMS is represented
logically in just one way - by values in tables.
2. The Guaranteed Access rule: Each item of data in an RDBMS is
guaranteed to be logically accessible by resorting to a combination of
table name, primary key value, and column name.
3. The Systematic Treatment of Null Values rule: Null values (distinct
from an empty character string or a string of blank characters and
distinct from zero or any other number) are supported in a fully
relational DBMS for representing missing
4. The Dynamic Online Catalog Based on the Relational Model rule:
The database description is represented at the logical level in the same
way as ordinary data, so that authorized users can apply the same
relational database.
5. The Comprehensive Data Sublanguage rule: A relational system
may support several languages and various modes of terminal for data
definition, view definition, data manipulation etc.
6. The View Updating rule: All views of the data which are
theoretically updatable must be updatable in practice by the DBMS.
Prepared by: Prof. P. B. Khairnar
, 7. The High-level Insert, Update, and Delete rule: The capability of
handling a base relation or a derived relation as a single database to
perform all DML operations.
8. The Physical Data Independence rule: Application programs and
terminal activities remain logically unchanged whenever any changes
are made in either storage representations or access methods.
9. The Logical Data Independence rule: Application programs and
terminal activities remain logically unchanged when information
preserving changes of any kind are made to the base tables.
10. The Integrity Independence rule: Integrity constraints must be
definable in the RDBMS sub-language and stored in the system
catalogue and not within individual application programs.
11. The Distribution Independence rule: An RDBMS has distribution
independence. Distribution independence implies that users should
not have to be aware of whether a database is distributed.
12. The No subversion rule: If the database has any means of handling
a single record at a time that low-level language must not be able
avoid the integrity rules which are expressed in a higher-level language
that handles multiple records at a time.
Prepared by: Prof. P. B. Khairnar
