The Trigger Name: T_CAL_BEF_HIS_TRG1
The trigger sublist 2:
The trigger sublist 3:
The trigger sublist 4:
-- -- -- -- -- -- -- -- Dumping Sorted Master the Trigger List -- -- -- -- -- -- -- --
The Trigger Owner: XHHBOLD
The Trigger Name: SMS_T_CAL_LAST
The Trigger Owner: XHHBOLD
The Trigger Name: T_CAL_LAST_TRG
-- -- -- -- -- -- -- -- Dumping Trigger Sublists -- -- -- -- -- -- -- --
The trigger sublist 0:
The trigger sublist 1:
The Trigger Owner: XHHBOLD
The Trigger Name: T_CAL_LAST_TRG
The trigger sublist 2:
The trigger sublist 3:
The Trigger Owner: XHHBOLD
The Trigger Name: SMS_T_CAL_LAST
The trigger sublist 4:
-- -- -- -- -- -- -- -- Dumping Sorted Master the Trigger List -- -- -- -- -- -- -- --
The Trigger Owner: XHHBOLD
The Trigger Name: SMS_T_ORI_LAST
The Trigger Owner: XHHBOLD
The Trigger Name: T_ORI_LAST_TRG
-- -- -- -- -- -- -- -- Dumping Trigger Sublists -- -- -- -- -- -- -- --
The trigger sublist 0:
The trigger sublist 1:
The Trigger Owner: XHHBOLD
The Trigger Name: T_ORI_LAST_TRG
The trigger sublist 2:
The trigger sublist 3:
The Trigger Owner: XHHBOLD
The Trigger Name: SMS_T_ORI_LAST
The trigger sublist 4:
-- -- -- -- -- -- -- -- Dumping Sorted Master the Trigger List -- -- -- -- -- -- -- --
The Trigger Owner: XHHBOLD
The Trigger Name: T_CAL_BEF_HIS_TRG2
The Trigger Owner: XHHBOLD
The Trigger Name: T_CAL_BEF_HIS_TRG1
-- -- -- -- -- -- -- -- Dumping Trigger Sublists -- -- -- -- -- -- -- --
The trigger sublist 0:

CodePudding user response:

Their top that great spirit support

CodePudding user response:

Above the table of the data volume change more often than not, is not recommended triggers, commonly used in some dictionary tables or base table to write a trigger, prevent mistakenly deleted, operating more by mistake

CodePudding user response:

I want to find a similar problem, don't know how to break, don't know the original poster can be solved

CodePudding user response:

Can do a plan task, delete the log on a regular basis

CodePudding user response:

Don't trigger