0
Want this question answered?
Be notified when an answer is posted
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.
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.
Which one of the following items would be 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.
Which option should we adopt to improve the database design of the organisation?
That would depend on what those specific options are. The options can only be determined by examining the flaws within the current database design of the organisation.
Explain pitfalls in relational database design?
One of the tenets of relational database design is "normalization". Normalization is the process of reducing a complex data structure into its simplest, most stable structure. In general, the process entails the removal of redundant attributes, keys, and relationships from a conceptual data model. In database design one has to make decisions about the trade offs offered by normalization. A completely normalized database can offer a great deal less redundancy and offer a infinite complexity and relational flexibility to the user/designer. On the other hand, this can get out of hand. The downside is that queries get overly complex and it can slow the database to a crawl as more and more data is accumulated. A simple example would be that of a database that represents an address book. The simplest design would be a flat database or a single table with columns like name, address, home phone, work phone. This would be a very fast, easily queried database but somewhat limited. What if you have someone who has more than two phone numbers? what if you want to put in their work address or the address of their vacation home. The fully normalized version of this database would have a core table for contacts that would link to a table of addresses, a table of phone numbers, a table of zip codes. There would also be tables called look up or type or category tables that would list the possible categories for phone numbers such as work, home, fax, cell etc.. as well as a table for address categories, work, home, vacation house etc.. you could also add a category table for the relationships between you and the contact and one for the relationships between contacts e.g, 'my friend', 'my boss', 'his sister', 'her uncle'. The Pitfall here is this database would quickly get too complicated for unsophisticated users to query and understand and it would get slow as more and more data was accumulated. Xequence-- The pitfalls in relational database design is that you must learn the system. This process of 'learning the system' will take some time. Another pitfall is that everything must have referential integrity. Not an easy task to think about. The last pitfall in a relational database design is the length of time it requires to build stored procedures and triggers. These values cannot insert null values into a [does not allow null] field that is relational to a foreign key table with more cannot insert nulls that have constraints if the values goes below 0 to email a man in Nantucket that his gridview errored out on line index 4 with his foreign key constraint. *breathe* It gets better..
What would be most likely to attract an angel investor?
A brand new database design company
How would you check a data model for redundancy?
Normalization.
Enterprises would be most likely to attract an angel investor?
a brand new database design company
What enterprise would be most likely to attract an angel investor?
A brand new database design company
How do you design forms in object oriented database?
A database is about storing data, not about creating forms. You would create the forms in some programming language - NOT something directly related to the database server - than have your forms, or rather your program in general, connect to the database.
If you took java one and two on an online college would you then be able to get a job as a java programmer?
Answer: sorry no =[ Answer: I would suspect you would require quite a bit more than that to do serious programming work. With what you know, are you able to: access a database? create a user interface? set up a client-server system? do you know about database normalization? These are but a few of the areas you might need, which are not included in basic courses.
What are poor design process?
Poor design processes would be where the design doesn't meet the specification and requirements agreed with the customer. If the customers needs aren't met then that forms bad relations with said customer
Why do you require a RegNo field in MS-access when you already have RollNo field?
That question cannot really be answered, as it is down to the data you have and the database you are trying to design. You may well need these fields and have one as a primary key and have another field unique. To properly design a database, a lot of thought has to go into it, especially if there is more than one table and there are relationships. Even for one table you would work out what fields you need and how you design them. So you may have a requirement for both of those fields. It is your design, not Access itself, that decides what fields you need.That question cannot really be answered, as it is down to the data you have and the database you are trying to design. You may well need these fields and have one as a primary key and have another field unique. To properly design a database, a lot of thought has to go into it, especially if there is more than one table and there are relationships. Even for one table you would work out what fields you need and how you design them. So you may have a requirement for both of those fields. It is your design, not Access itself, that decides what fields you need.That question cannot really be answered, as it is down to the data you have and the database you are trying to design. You may well need these fields and have one as a primary key and have another field unique. To properly design a database, a lot of thought has to go into it, especially if there is more than one table and there are relationships. Even for one table you would work out what fields you need and how you design them. So you may have a requirement for both of those fields. It is your design, not Access itself, that decides what fields you need.That question cannot really be answered, as it is down to the data you have and the database you are trying to design. You may well need these fields and have one as a primary key and have another field unique. To properly design a database, a lot of thought has to go into it, especially if there is more than one table and there are relationships. Even for one table you would work out what fields you need and how you design them. So you may have a requirement for both of those fields. It is your design, not Access itself, that decides what fields you need.That question cannot really be answered, as it is down to the data you have and the database you are trying to design. You may well need these fields and have one as a primary key and have another field unique. To properly design a database, a lot of thought has to go into it, especially if there is more than one table and there are relationships. Even for one table you would work out what fields you need and how you design them. So you may have a requirement for both of those fields. It is your design, not Access itself, that decides what fields you need.That question cannot really be answered, as it is down to the data you have and the database you are trying to design. You may well need these fields and have one as a primary key and have another field unique. To properly design a database, a lot of thought has to go into it, especially if there is more than one table and there are relationships. Even for one table you would work out what fields you need and how you design them. So you may have a requirement for both of those fields. It is your design, not Access itself, that decides what fields you need.That question cannot really be answered, as it is down to the data you have and the database you are trying to design. You may well need these fields and have one as a primary key and have another field unique. To properly design a database, a lot of thought has to go into it, especially if there is more than one table and there are relationships. Even for one table you would work out what fields you need and how you design them. So you may have a requirement for both of those fields. It is your design, not Access itself, that decides what fields you need.That question cannot really be answered, as it is down to the data you have and the database you are trying to design. You may well need these fields and have one as a primary key and have another field unique. To properly design a database, a lot of thought has to go into it, especially if there is more than one table and there are relationships. Even for one table you would work out what fields you need and how you design them. So you may have a requirement for both of those fields. It is your design, not Access itself, that decides what fields you need.That question cannot really be answered, as it is down to the data you have and the database you are trying to design. You may well need these fields and have one as a primary key and have another field unique. To properly design a database, a lot of thought has to go into it, especially if there is more than one table and there are relationships. Even for one table you would work out what fields you need and how you design them. So you may have a requirement for both of those fields. It is your design, not Access itself, that decides what fields you need.That question cannot really be answered, as it is down to the data you have and the database you are trying to design. You may well need these fields and have one as a primary key and have another field unique. To properly design a database, a lot of thought has to go into it, especially if there is more than one table and there are relationships. Even for one table you would work out what fields you need and how you design them. So you may have a requirement for both of those fields. It is your design, not Access itself, that decides what fields you need.That question cannot really be answered, as it is down to the data you have and the database you are trying to design. You may well need these fields and have one as a primary key and have another field unique. To properly design a database, a lot of thought has to go into it, especially if there is more than one table and there are relationships. Even for one table you would work out what fields you need and how you design them. So you may have a requirement for both of those fields. It is your design, not Access itself, that decides what fields you need.
What schools offer classes on Microsoft access online?
Microsoft Access is a database management program used in web design systems. Schools that would offer classes in Access would be based around IT or web design platforms.
How do you design and develop an information system?
In order to design and develop an information system, you would need to consider its purpose. This will help in setting up the database and settings which will be used in managing the information system.
