Arockia Raj wrote:Is there any way to control or limit the number of concurrent DCN notification or is there any other solution solution..
As mentioned by Martin, according to the
documentation it is mentioned as one of the best practices to use it only when your tables are mostly read-only (and modifications are the exception rather than the rule).
Best Practices wrote:For best performance of change notification, the following guidelines are presented. Registered objects are few and mostly read-only and that modifications to those objects are the exception rather than the rule. If the object is extremely volatile, then it will cause a large number of invalidation notifications to be sent, and potentially a lot of storage in the invalidation queue on the server. If there are frequent and a large number of notifications, it can slow down OLTP throughput due to the overhead of generating the notifications.It is also a good idea to keep the number of duplicate registrations on any given object low (ideally one) in order to avoid the same notification message being replicated to multiple recipients.
Hope it helps!
Kind regards,
Roel