No. Basic notifications do nothing to create or drop DB objects. The buffer table and trigger are to be created and dropped manually. The value of this approach:
-
Some DB teams grant create/drop privileges to only select accounts. If this is a restriction, the insert/update/delete notifications cannot be used.
-
Prior to the suspend state being added (I don’t know what version introduced this), one could only disable a notification. This would drop the buffer table and trigger, which could cause undesired loss of events.
My preference is always to use basic notifications. That way, one doesn’t have to remember the difference between disable and suspend, and one won’t lose events if someone accidentally disables a notification.
#Integration-Server-and-ESB#Flow-and-Java-services#webMethods