0
Which one of the following items would be most likely to keep in a database?
Wiki User
∙ 9y ago
Databases can store any manner of information in a digital format so it is easy to store, organize, save, send, and share.
Wiki User
∙ 9y ago
Add your answer:
Earn +20 pts
Why would you sort a database?
You would sort a database to make it easier for a computer to recall information.
Why is quality of Data important?
There is a saying in the database industry - GIGO. It stands for garbage in Garbage out. The point of a database is to maintain data in a way that it has a use. For example, in a business a database might be used for inventory. What good would it be if the database didn't contain the right information on quantity and price. Also when you sell something you would like to have its quantity decremented in the database. If this didn't happen reliably you have a big problem. There are other factors in data quality that might be associated with the precision of the data. For example you might have a piece of data stored as an integer, but find out later that you actual need floating point for more precision in your queries.
Which ordered pair replacement would make the following relation a function?
The following is the answer.
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.
What are the various reasons that lead to the occurrence of NULL values in relations?
A given field in a database table might be for a values that, in certain case, no such values exist or can be determined. For example, in an employee database, a field might be a foreign key to that employee's direct manager. However, in the case of the CEO, there is no such person. In that case, the field would be set to Null.
What items would you most likely keep in a database?
Address
What items would you most likely keep in database?
Address
What items would you most likely keeping a database?
Address
What items would you be most likely to keep in a database?
address book
Which one of the following items would most likely to keep in a database?
Databases can store any manner of information in a digital format so it is easy to store, organize, save, send, and share.
If a database required regular additions of new records which of the following would likely be a good tool to use?
forms
What do you most likely keep in a database?
Important records, such as a financial statement is an item that you would be most likely to keep in a database.
What would you most likely keep in a database?
Address
Which items you would most likely to keep in your database?
If you are running a business you would want an easy way to keep track of your customers and their accounts payable. You can also track employees in the database (earnings, deductions, etc). You can also keep an active inventory of your warehouse stock so at a quick glance you know what items you have and which need to be ordered without having to manually check the shelves every day. There are many other uses for a database in our daily lives.
What items would be increased by the sale of the old equipment?
The "following" items would not be affected in the least!
What items would you keep in your database?
A database should be dedicated to one sort of information. A common mistake designers of database systems make is combining unrelated information, leading to many issues.
What would be most likely to attract an angel investor?
A brand new database design company
