Jiwa

Customer on 7.2.1 SR4, reporting poor performance of cashbook receipts with large batches, including slow refresh times.

The problem was reported on a batch of only 65 receipts, but could the problem reported in https://forums.jiwa.com.au/viewtopic.php?f=26&t=610&hilit=cashbook+receipt+performance be affecting them in the standard UI as well, and would patching their .EXE for LARGEADDRESSAWARE help?

I have asked them to check RAM usage for JIWA.EXE next time they're having the problem.

I would start here https://docs.jiwa.com.au/display/J7UG/S ... eving+data, you may find rebuilding the indexes etc may help, also check the databases compatibility level is the same as the server.

The other thing is I would try is possibly lowering the transient failure setting in System setting, if its a networking/cabling issue lowering the retries temporarily and seeing it falls over might point you in the right direction if the problem isn't Jiwa itself.

SBarnes wrote:I would start here https://docs.jiwa.com.au/display/J7UG/S ... eving+data, you may find rebuilding the indexes etc may help, also check the databases compatibility level is the same as the server.

All their indexes were rebuilt after we upgraded them at the end of January, which also involved a whole new server and SQL upgrade, so I'd be slightly surprised if it's that. But then they also have a tendency to 'experiment', so I may need to check up on that.

SBarnes wrote:The other thing is I would try is possibly lowering the transient failure setting in System setting, if its a networking/cabling issue lowering the retries temporarily and seeing it falls over might point you in the right direction if the problem isn't Jiwa itself.

Thanks, I've suggested trying this - they've had a few weird problems. I traced some to MS Access queries holding locks on the database, but others seem to have no cause. If nothing else it may help them isolate some of their troubles.

so, naturally, this past week (the customer's busy week for cashbook receipts) they had no problems....

It might just be the view that backs the main MS Access query that they all use. The one that I added a bunch of NOLOCK hints to when I was there the week before.

At least that's what I'm telling myself at the moment.