Biso007
23rd December 2004, 03:26 PM
Hi folks,
After few weeks of experience with WM2003SE (thx to all work done here!), I noticed some more degraded performance with time. I checked the DB_notify_queue database and found it with 213 recoreds despite that I have the clear_notify fix in the startup :shock: ... the average should not exceed 30 records!!
I ckecked the DB file and found that the events of type SCRIPT: 0x000 were NOT removed by the fix. This event is generated for each missed call, and I have a lot since I use CallerFirewall ;)
Also, if you are using StopTime application, it will add new duplicate record each time you modify its settings. I used the CheckNotification s/w to remove these events.
May this help you to enjoy more stable SE
After few weeks of experience with WM2003SE (thx to all work done here!), I noticed some more degraded performance with time. I checked the DB_notify_queue database and found it with 213 recoreds despite that I have the clear_notify fix in the startup :shock: ... the average should not exceed 30 records!!
I ckecked the DB file and found that the events of type SCRIPT: 0x000 were NOT removed by the fix. This event is generated for each missed call, and I have a lot since I use CallerFirewall ;)
Also, if you are using StopTime application, it will add new duplicate record each time you modify its settings. I used the CheckNotification s/w to remove these events.
May this help you to enjoy more stable SE