TechTip: Changing Triggers on a Busy System

[Guest.Visitor]

** This thread discusses the article: TechTip: Changing Triggers on a Busy System (http://www.mcpressonline.com/index.php?option=com_content&view=article&id=3856) **
** This thread discusses the Content article: TechTip: Changing Triggers on a Busy System (http://www.mcpressonline.com/index.php?option=com_content&view=article&id=3856) **
0

[Guest.Visitor]

** This thread discusses the article: TechTip: Changing Triggers on a Busy System (http://www.mcpressonline.com/index.php?option=com_content&view=article&id=3856) **
As a software development company this was an issue we resolved several years ago. All trigger programs only put entries onto data queues they never do any "data processing". They only ever need to be modified if the file definition is changed and then there is no issue over locks by the database. Whenever the real processing has to change it is the DataQ server program which gets replaced and this is never a problem.

[daves@bfcsoftware.com]

** This thread discusses the article: TechTip: Changing Triggers on a Busy System (http://www.mcpressonline.com/index.php?option=com_content&view=article&id=3856) **
My understanding of data queues is that they do not reuse deleted records and therefore have to be deleted and recreated periodically to reclaim the wasted space. If this is true wouldn't you still have to stop all processing to do this or take the risk of the trigger writing to a data queue that isn't there?