2013
DOI: 10.5121/ijdms.2013.5303
|View full text |Cite
|
Sign up to set email alerts
|

Algorithm for Relational Database Normalization Up to 3NF

Abstract: ABSTRACT

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
12
0

Year Published

2014
2014
2022
2022

Publication Types

Select...
6
2

Relationship

0
8

Authors

Journals

citations
Cited by 22 publications
(12 citation statements)
references
References 6 publications
(5 reference statements)
0
12
0
Order By: Relevance
“…The Cross Join produces a result set which includes number of tuple in the first relation multiplied by the number of tuple in the second relation, if there is no where clause is used with Cross Join syntax. This type of query results is called as Cartesian product [17]. If the where clause statement is used with Cross Join.…”
Section: Related Workmentioning
confidence: 99%
“…The Cross Join produces a result set which includes number of tuple in the first relation multiplied by the number of tuple in the second relation, if there is no where clause is used with Cross Join syntax. This type of query results is called as Cartesian product [17]. If the where clause statement is used with Cross Join.…”
Section: Related Workmentioning
confidence: 99%
“…G.Sunitha, Dr.A.Jaya, "A KNOWLEDGE BASED APPROACH FOR AUTOMATIC DATABASE NORMALIZATION", [9] aims to provide automatic normalization of databases up to 3NF in order to reduce the time consuming in manually normalization. Moussa Demba, "ALGORITHM FOR RELATIONAL DATABASE NORMALIZATION UP TO 3NF", [2] the author proposed an algorithmic approach for database normalization up to third normal form by taking into account all candidate keys, including the primary key.…”
Section: Pb Alappanavar Dhiraj Patil Radhika Grover Srishtimentioning
confidence: 99%
“…It usually involves dividing a database into two or more tables and defining relationships between the tables. The objective is to isolate data so that additions, deletions, and modifications of a field can be made in just one table and then propagated through the rest of the database via the defined relationships [2].…”
Section: Introductionmentioning
confidence: 99%
“…This strategy reduces memory and increases processing speed. Another proposal that allows users normalize up to 3NF considers all possible candidate keys . In a first stage, it eliminates functional dependencies and then normalizes relations using fields as input.…”
Section: Introductionmentioning
confidence: 99%