Latest Activity In Study Groups

Join Your Study Groups

VU Past Papers, MCQs and More

We non-commercial site working hard since 2009 to facilitate learning Read More. We can't keep up without your support. Donate.

Discussion Topic


Suppose, you are working in a company as a database expert and company wants to create its database where most of the operations are write intensive and database needs to be updated on regular basis. Whereas, some of the tasks require frequent read operations to display important reports to users. While designing database, company also wants to make sure the efficient use of storage devices during data storage.

Now, you are required to suggest your company whether it should implement Indexing while designing its database or not? Provide at least two proper reasons to support your answer.

Read the following instructions carefully before sending your comments:


  1. GDB will have weight-age of 5% of your total subject marks.
  2. Your discussion must be based on logical facts.
  3. You should post your comments on the Graded Discussion Board & not on the Regular MDB. Both will run parallel to each other during the time specified above.
  4. Your comments should be relevant to the topic i.e. clear and concise (Maximum 4-5 lines answer).
  5. Books, websites and other reading material may be consulted before posting your comments. (Do not copy the material as it is.)
  6. No extra time will be given for discussion.
  7. You cannot participate in the discussion after the due date or through e-mail.

Views: 1728

Replies to This Discussion

Indexes speed up retrievals but slow down inserts and deletes, as well as updates of values in indexed columns. That is, indexes slow down most operations that involve writing. This occurs because writing a row requires writing not only the data row, it requires changes to any indexes as well. The more indexes a table has, the more changes need to be made, and the greater the average performance degradation. Most tables receive many reads and few writes, but for a table with a high percentage of writes, the cost of index updating might be significant. Avoid Indexes: If you don’t need an index to help queries perform better, don’t create it. Disk Space: An index takes up disk space, and multiple indexes take up correspondingly more space. This might cause you to reach a table size limit more quickly than if there are no indexes. Avoid indexes wherever possible.

kia ye theek hay

koi to solution post kr do


© 2022   Created by + M.Tariq Malik.   Powered by

Promote Us  |  Report an Issue  |  Privacy Policy  |  Terms of Service