I know this is an old post but I thought it was worth adding that you can disable all the triggers in code using: And
You can find the option details in the docs for v11: http://dcx.sybase.com/1100/en/dbadmin_en11/fire-triggers-option.html Also for what it is worth i found the same in the v7 and v9 docs as well. You're not mistaken, even though the Help doesn't mention that fact.
(30 Aug '12, 10:23)
Breck Carter
Replies hidden
1
As this may also influence RI logic (i.e. cascading deletes and the like), I'm really surprised that this option can be used connection-specific - "handle with care", they say:)
(30 Aug '12, 12:07)
Volker Barth
Yes, as it requires DBA authority, the "careful handling" is given by nature:)
(30 Aug '12, 12:09)
Volker Barth
2
The anal-retentive part of me wants to highlight that the original question asked about disabling "a" trigger, but setting the fire_triggers database option will disable "ALL" triggers in the database, including system generated triggers used for referential integrity on foreign keys. I think the original answers from Mark and Thomas are better suited to disabling a single trigger.
(30 Aug '12, 12:37)
Reg Domaratzki
Replies hidden
I agree with you Reg, this post was only intended as an addition. I would only use it in a rare situation when I had little choice.
(31 Aug '12, 08:17)
Robert2
|