Is data duplication is a desirable aspect of a database?
No it is not. A well designed database will have no duplication. Duplication of data takes up more space. It can also lead to inconsistencies in the data. If the same data is there more than once, it can sometimes that not all copies of it are changed when they have to be. So for example, you could have a person listed twice in a database. If they got a new phone number and this was only changed in one of the entries for them on the database, you would now have the same person listed twice, but with each having a different phone number. If they are on the system once only, then there cannot be those kinds of inconsistencies.No it is not. A well designed database will have no duplication. Duplication of data takes up more space. It can also lead to inconsistencies in the data. If the same data is there more than once, it can sometimes that not all copies of it are changed when they have to be. So for example, you could have a person listed twice in a database. If they got a new phone number and this was only changed in one of the entries for them on the database, you would now have the same person listed twice, but with each having a different phone number. If they are on the system once only, then there cannot be those kinds of inconsistencies.No it is not. A well designed database will have no duplication. Duplication of data takes up more space. It can also lead to inconsistencies in the data. If the same data is there more than once, it can sometimes that not all copies of it are changed when they have to be. So for example, you could have a person listed twice in a database. If they got a new phone number and this was only changed in one of the entries for them on the database, you would now have the same person listed twice, but with each having a different phone number. If they are on the system once only, then there cannot be those kinds of inconsistencies.No it is not. A well designed database will have no duplication. Duplication of data takes up more space. It can also lead to inconsistencies in the data. If the same data is there more than once, it can sometimes that not all copies of it are changed when they have to be. So for example, you could have a person listed twice in a database. If they got a new phone number and this was only changed in one of the entries for them on the database, you would now have the same person listed twice, but with each having a different phone number. If they are on the system once only, then there cannot be those kinds of inconsistencies.No it is not. A well designed database will have no duplication. Duplication of data takes up more space. It can also lead to inconsistencies in the data. If the same data is there more than once, it can sometimes that not all copies of it are changed when they have to be. So for example, you could have a person listed twice in a database. If they got a new phone number and this was only changed in one of the entries for them on the database, you would now have the same person listed twice, but with each having a different phone number. If they are on the system once only, then there cannot be those kinds of inconsistencies.No it is not. A well designed database will have no duplication. Duplication of data takes up more space. It can also lead to inconsistencies in the data. If the same data is there more than once, it can sometimes that not all copies of it are changed when they have to be. So for example, you could have a person listed twice in a database. If they got a new phone number and this was only changed in one of the entries for them on the database, you would now have the same person listed twice, but with each having a different phone number. If they are on the system once only, then there cannot be those kinds of inconsistencies.No it is not. A well designed database will have no duplication. Duplication of data takes up more space. It can also lead to inconsistencies in the data. If the same data is there more than once, it can sometimes that not all copies of it are changed when they have to be. So for example, you could have a person listed twice in a database. If they got a new phone number and this was only changed in one of the entries for them on the database, you would now have the same person listed twice, but with each having a different phone number. If they are on the system once only, then there cannot be those kinds of inconsistencies.No it is not. A well designed database will have no duplication. Duplication of data takes up more space. It can also lead to inconsistencies in the data. If the same data is there more than once, it can sometimes that not all copies of it are changed when they have to be. So for example, you could have a person listed twice in a database. If they got a new phone number and this was only changed in one of the entries for them on the database, you would now have the same person listed twice, but with each having a different phone number. If they are on the system once only, then there cannot be those kinds of inconsistencies.No it is not. A well designed database will have no duplication. Duplication of data takes up more space. It can also lead to inconsistencies in the data. If the same data is there more than once, it can sometimes that not all copies of it are changed when they have to be. So for example, you could have a person listed twice in a database. If they got a new phone number and this was only changed in one of the entries for them on the database, you would now have the same person listed twice, but with each having a different phone number. If they are on the system once only, then there cannot be those kinds of inconsistencies.No it is not. A well designed database will have no duplication. Duplication of data takes up more space. It can also lead to inconsistencies in the data. If the same data is there more than once, it can sometimes that not all copies of it are changed when they have to be. So for example, you could have a person listed twice in a database. If they got a new phone number and this was only changed in one of the entries for them on the database, you would now have the same person listed twice, but with each having a different phone number. If they are on the system once only, then there cannot be those kinds of inconsistencies.No it is not. A well designed database will have no duplication. Duplication of data takes up more space. It can also lead to inconsistencies in the data. If the same data is there more than once, it can sometimes that not all copies of it are changed when they have to be. So for example, you could have a person listed twice in a database. If they got a new phone number and this was only changed in one of the entries for them on the database, you would now have the same person listed twice, but with each having a different phone number. If they are on the system once only, then there cannot be those kinds of inconsistencies.
Steve
Professor
Fran
