It could be, and could not be at the same time. I'm going to use SQL for an example. Say you have a website, and a user signs up. You would have a users table, first off to store the users information. Then, you would have another table with the actual content that that user has stored. The repeating field would be the USERID.
But, if you have the same data stored twice in two different tables, that's a bad thing.
yes
In database there are number of issues to be handled ,like redundant data, inconsistent data, unorganized data etc. Redundancy of data is the repetitive data that is taking the storage unnecessarily . So the redundant data must be removed or at least reduced.
yes. data redundancy is where there is duplication of data in a database. when this happens, anyone who has to make updates to a table in a database (that is, make changes to the database) will have to change that particular data that has been duplicated so many times in so many places. this creates a problem and it is not always going to be possible for a person to change everything correctly. this therefore leads to inconsistencies in the database. hope this helps.
Reduced data redundancy, Improved data integrity, Shared data, Easier access, Reduced development time
In a database management system (DBMS), an attribute may describe a component of the database, such as a table or a field, or may be used itself as another term for a field. Commonly we can say that an attribute is a "propety" of a database field or its a characteristic or facet of the data field..
yes
Database is collection of some inter related records . And yes, data redundancy be completely eliminated when database approach is used.
it is the process of finding the redundancy.
Avoid redundancy, for instance.
Redundancy means duplicacy of data or repetitive data. In distributed database case the data is stored in different systems . So the answers is yes there can be redundancy of records / data.In distributed database , data is stored in different systems. Since the data is distributed there is redundancy of records.
Database Normalization is the process of organizing the fields and tables of a relational database to minimize redundancy and dependency
this is true!
its called data redundancy.
In non-database systems each application has its own private files. This can often lead to redundancy in stored data, with resultant waste in storage space. In a database the data is integrated. The database may be thought of as a unification of several otherwise distinct data files, with any redundancy among those files partially or wholly eliminated. Data integration is generally regarded as an important characteristic of a database. The avoidance of redundancy should be an aim, however, the vigour with which this aim should be pursued is open to question. Redundancy is * direct if a value is a copy of another * indirect if the value can be derived from other values: ** simplifies retrieval but complicates update ** conversely integration makes retrieval slow and updates easier * Data redundancy can lead to inconsistency in the database unless controlled. * the system should be aware of any data duplication - the system is responsible for ensuring updates are carried out correctly. * a DB with uncontrolled redundancy can be in an inconsistent state - it can supply incorrect or conflicting information * a given fact represented by a single entry cannot result in inconsistency - few systems are capable of propagating updates i.e. most systems do not support controlled redundancy.
data redundancy
chandranana explain the characteristic of database?
A database is a collection of interrelated data and the advantages of a database are ensured efficiency, standardized data, maintainable data, integrated data, reduced redundancy of data.