Why Disable Constraints?
During day-to-day operations, constraints should always be enabled. In certain situations, temporarily disabling the integrity constraints of a table makes sense for performance reasons. For example: • When loading large amounts of data into a table using SQL*Loader • When performing batch operations that make massive changes to a table (such as changing each employee number by adding 1000 to the existing number) • When importing or exporting one table at a time Temporarily turning off integrity constraints can speed up these operations.
