Feedback
Did this article resolve your question/issue?

   

Article

Are triggers disabled during dump & load operations?

Information

 
TitleAre triggers disabled during dump & load operations?
URL NameAre-triggers-disabled-during-dump-load-operations
Article Number000185337
EnvironmentProduct: OpenEdge
Version: All supported versions
OS: All supported platforms
Question/Problem Description
Are triggers disabled during dump & load operations?
Steps to Reproduce
Clarifying Information
Error Message
Defect/Enhancement Number
Cause
Resolution
When utilizing unmodified versions of the Data Administration and proutil tools to perform a dump and load, triggers are automatically disabled. This is not the case when the dump and load is being performed through 4GL/ABL. In this case the triggers will have to be disabled through the application code. 
Workaround
Notes
References to Other Documentation:

OpenEdge Data Management: Database Administration : Maintaining and Monitoring Your Database : Dumping and Loading : Bulk loading : Loading table contents with the Bulk Loader qualifier
OpenEdge Development: ABL Reference : ABL Syntax Reference : DISABLE TRIGGERS statement
 
Last Modified Date3/2/2016 9:12 PM
Attachment 
Files
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.