Principles Relational Database


Hello and welcome to everyone. Today we will learn about principles of relational database that are proposed by Edgar F. Codd in 1969.



C# basic course click on: https://www.udemy.com/learn-csharp-with-sagar-jaybhay/ 
Web API 2- .Net Core In depth In 5 Hours click on: https://www.udemy.com/web-api-2-net-core-in-depth-in-5-hrs-with-sagar-jaybhay/

Principle of Relational database concepts firstly proposed by Edgar F. Codd in 1969. Database tables used to store data and these tables have relations to other tables in Relational database. When you understanding following principles then it will help you to develop and design a relational database.
Following are the E.F. Codd principles of a relational database. 
1. Relational Databases use a table to store data and the stored data tables have relations to other tables. 

2. Relational Databases are the most used databases in the world such as smartphones, desktops, automobiles, etc. and these all information logically represent in tables. All these data are kept in column and rows in the table. 

3. Relational Database you can access data logically by primary key, table, column. The primary key is optional and you rarely see database tables without a primary key, but this is a distinct database column or columns that are used to uniquely identify a database record from the database. 

4. Null values in the database must be consistently preserved as missing information not as unfilled strings or blanks or zero. 

5. Structure of the database must keep in an online collection which can be inquired by official users or must be stored in the database just as regular data is.

6. A relational database should be reachable by a language supporting all of the following:
a. Data definition
b. Data Manipulation
c. View definition
d. Authorization
e. Integrity constraints
f. Transactions management operations. 

7. All views that is academically updatable of their base tables and also updatable by the system.

8. In Relational database a single operation must be supported insert, retrieve, delete, update data in that database. 

9. Application level programs and fatal actions linger logically unaffected whenever any changes are made in either storage demonstrations. 

10. Application level programs and fatal actions linger logically unaffected when information conserving changes of any kind that academically permit un-impairment are made to the base tables. 

11. Integrity constraints exact to a specific relational database must be definable in the relational data available and storable in the string, not in the application programs.

12. Data is distributed over various locations should not be visible to end users.

13. If a relational database single record at a time language then low level can’t be used to sidestep the integrity rules and constraints expressed in the multiple records at a time language. 

C# basic course click on: https://www.udemy.com/learn-csharp-with-sagar-jaybhay/ 
Web API 2- .Net Core In depth In 5 Hours click on: https://www.udemy.com/web-api-2-net-core-in-depth-in-5-hrs-with-sagar-jaybhay/

Visit our website:- 
https://expertwithsagarjaybhay.com/

Comments

Popular posts from this blog

ALTER statement in MySQL

Order By Clause in MySQL

MySQL Constraint – UNIQUE