Q
Problem solve Get help with specific problems with your technologies, process and projects.

Why disable a table for table update?

It is said that when we update large data from a table, the index must be disabled. Can you give the reason for this as the index will rebuild or update when we enable it?
Many people drop an index before large DML operations on a trigger. The reason is that each affected row will make a change to the table's indexes. For every INSERT, there is a index value inserted into the index. For every DELETE, the index is modified. If you are performing many DML statements against the table, it is often quicker to drop the trigger, perform your batch DML statements, and then recreate the trigger than it is to leave the trigger in place. Keep in mind that your application will not be able to use the trigger if it is dropped, even momentarily.

Dig Deeper on Oracle database design and architecture

Have a question for an expert?

Please add a title for your question

Get answers from a TechTarget expert on whatever's puzzling you.

You will be able to add details on the next page.

Start the conversation

Send me notifications when other members comment.

Please create a username to comment.

-ADS BY GOOGLE

SearchDataManagement

SearchBusinessAnalytics

SearchSAP

SearchSQLServer

TheServerSide.com

SearchDataCenter

SearchContentManagement

SearchHRSoftware

Close