With current Windows Connect:Express versions, when notifications are enabled, notification records are added at run-time in the local database, even when they are fully processed (notifications messages sent), and they remain there, possibly very numerous, until the monitor is restarted. It is a major issue if the monitor is rarely restarted...
We moreover noticed that past a certain amount of records, all file transfer processes take more time and more CPU.
Enabling notification records purge at monitor startup then becomes mandatory, but as records are deleted one by one, the purge process may last a very long time before the monitor's availability for transfers.
So it is very annoying and the purge process should be available at run-time,
* at least as a scheduled internal task (as it is done for requests)
* and if possible, manually triggerable by admin user.
How will this idea be used?
When notifications are enabled (needed for us for file transfer statistics processes), without notification records purge, there is a time when monitor becomes unusable with transfers abnormally long and random delays.
|What is your industry?||Banking|
|What is the idea priority?||High|
|Link to original RFE|