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:
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